When a schema has a simple (non-list) complex property, the storage model is an additional child row in the "hierarchy" table. However this row is created lazily on first read access (session.addChildNode in SQLSession.makeProperties), which is a problem in situations with concurrent reads.
To improve this, make sure the child row in the hierarchy table is created at document creation time.
- depends on
-
NXP-11397 Optimize document write
- Resolved
- is required by
-
NXP-12269 Content view tab actions are unresponsive
- Resolved
-
NXP-12324 Publishing a document with thumbnail fails
- Resolved
-
NXP-12098 Cannot get thumbnails for office documents
- Resolved
-
NXP-12907 Pre-creation of complex properties to avoid concurrency issues
- Resolved
-
NXP-12957 Fix recursive removal under MySQL
- Resolved