[PHPCR-69] persist referrers Created: 04/Jun/12  Updated: 11/Jan/13  Resolved: 11/Jan/13

Status: Resolved
Project: Doctrine PHPCR
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: David Buchmann Assignee: Lukas Kahwe
Resolution: Fixed Votes: 0
Labels: None


 Description   

phpcr knows reference and referrer (backlink). the reference is a property of a node with a defined name. the referrer is an information on the node without a property name in PHPCR. we have the annotation @Referrers to map this information onto a document field. the annotation can take an optional filter argument to only use references pointing to this node with a specific phpcr name.

we could add something like the cascade option found in the orm to allow assigning a document to a referrer property and automatically persist it. we will need to explicitly specify the reference property name to be used on the source document in this case (orm uses mappedBy for this)

github user mdekrijger started working on this. today, he wrote: Adding the annotations was quite easy, still figuring out the unitofwork where the actual processing must be implemented. Currently I can't spend much more time on it until end of june. If it isn't done yet by that time, I surely will pick it up from there.



 Comments   
Comment by M. de Krijger [ 27/Jun/12 ]

Could someone assign this to me? If not I will just comment this issue when new info is available

Comment by Lukas Kahwe [ 30/Aug/12 ]

hmm .. bah i guess its not possible to assign the ticket for you unless someone upgrades your account for which i dont have the permissions .. so just keep commenting i guess

Comment by Lukas Kahwe [ 09/Jan/13 ]

i guess this is now fixed?

Comment by David Buchmann [ 10/Jan/13 ]

yes, i think so. you implemented that with the cascading configuration options, didn't you?

Comment by Lukas Kahwe [ 11/Jan/13 ]

yes .. referrer changes are cascaded with control over the cascading

Generated at Wed Jul 23 17:33:53 UTC 2014 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.