phpcr-odm
phpcr-odm copied to clipboard
doctrine
Doctrine PHPCR ODM
### What As per discussion with @dantleech, the current `UnitOfWork` identity map is very messy, and unlikely to be compatible with the upcoming [Ocramius/ChangeSet](https://github.com/Ocramius/ChangeSet) rework. ### Why There are also...
In my EventSubscriber I am creating a new Document on the preUpdate or prePersist events. ``` php public function prePersist(LifecycleEventArgs $args) { $doc = new Document(); // initialization here ......
right join are currently not supported by all RDBMS and so Jackalope Doctrine DBAL may fail due to its current implementation https://github.com/doctrine/phpcr-odm/blob/master/lib/Doctrine/ODM/PHPCR/Translation/TranslationStrategy/ChildTranslationStrategy.php#L167 will lead to a right join in Doctrine...
The autoname id strategy could use some tweaks: - [ ] A way to specify an optional nameHint for addNodeAutoNamed - [ ] The strategy should check if there is...
I think it is. AFAIK the way to do this current is: ``` $qb->where()->eq()->field('c.address')->literal($address->getUuid()); ``` We could do something like: ``` $qb->where()->eq()->field('c.address')->uuidOf($address); ``` Or automatically cast referenceable objects to uuids:...
in #446 i add validation on the Child mapping so that you can't misuse that field to persist a document that is not attached to that field. we could do...
By now there are a lot of exception messages spread all over the code. They should be moved to factory methods of the respective exception classes, and cleaned to be...
see also #358 which is about improving the autoname id strategy. see for example https://github.com/doctrine/doctrine2/pull/206 note that "id" for phpcr-odm is the phpcr path. so this is not the same...
as discussed in https://github.com/doctrine/phpcr-odm/pull/268 we should implement UnitOfWork::isScheduledDocument and isScheduledFor\* other than isScheduledForInsert.
see http://www.day.com/specs/jcr/2.0/23_Orderable_Child_Nodes.html in general support for child ordering tends to increase overhead in most implementations, so it may be disabled or not even supported.