Maintenance release with lots of new features and cleanups.
-
Various bugfixes have been merged.
-
2014-01-08: The fetch depth performance optimization is now fully supported.
-
2014-01-08: You now get a RepositoryException if you try to overwrite one of the built-in node types. In 1.0, you got no exception but the custom type with the same name as a built-in type was simply ignored.
-
2014-01-07: We now properly support LENGTH in queries. This required a change to the stored data. To update existing installations, you can use this migration: https://github.com/wjzijderveld/jackalope-doctrine-dbal-length-migration
-
2014-01-05: Allowing to set a closure for a custom uuid generator. Set the parameter
jackalope.uuid_generator
to a function returning a UUID string and pass it as parameter to the repository factory. -
2014-01-04: mix:lastModified is now handled automatically. To disable, set the option jackalope.auto_lastmodified to
false
. -
2013-12-26: cleanup of phpcr-utils lead to adjust cli-config.php.dist. If you use the console, you need to sync your cli-config.php file with the dist file.
-
2013-12-14: Added support for logging PHPCR database queries.
-
2013-06-07: [#75] split the references into 2 tables
-
This splits the phpcr_nodes_foreignkeys into two separate tables
-
Improves performance and allows using native deferred FK capabilities in the future
-
Migration steps
- run
bin/jackalope jackalope:init:dbal --dump-sql
- Copy and execute all tables, indexes etc related to
phpcr_nodes_references
andphpcr_nodes_weakreferences
. - Run the following SQL statements:
- INSERT INTO phpcr_nodes_references ( source_id, source_property_name, target_id ) SELECT source_id, source_property_name, target_id FROM phpcr_nodes_foreignkeys WHERE type = 9;
- INSERT INTO phpcr_nodes_weakreferences ( source_id, source_property_name, target_id ) SELECT source_id, source_property_name, target_id FROM phpcr_nodes_foreignkeys WHERE type = 10;
- DROP TABLE phpcr_nodes_foreignkeys;
- run
-
2013-06-01: [#109] ensure data is stored as UTC and returned in the default TZ
-
This enables consistent search query behavior regardless of the timezone used
-
Any existing stored nodes need to be modified, so that they are stored again to benefit from this change.