To my understanding, KeyedRecord as well as KeyedField should provide the basis to implement relationship between model objects. If in my model object I have a relationship with another model object this will required the referred class to be at least a KeyedRecord. Such "ReferenceField" similar to the MappedForeignKey in Mapper, will have the same basic type of the KeyField in the referred KeyedRecord. Unfortunately in order to complete the design of a ReferenceField, it is required a "getInstance" or "find" method to load the object corresponding to the key. Implementation of this method is strictly related to the persistence backend but a generic definition should be inserted in MetaRecord (or better KeyedMetaRecord). Situation is even more complicated when yu have hierarchical (one to many) or even many to many relationship. I am studying sources from the recent addition to Mapper to get inspiration. In the ongoing jsr-170 backend to Record this is the way I am following even if after many redesigns some docs and support from the community on how to implements custom record backedn would be more than welcome.
Regards Giuseppe In my ongoing implementation of a jsr-170 backend for Record is not using KeyedRecord On 31 Lug, 13:18, Timothy Perrett <timo...@getintheloop.eu> wrote: > Guys, > > What is the intended implementation of KeyedRecord? The work done so > far on DBRecord appears not to use it? > > When / How should one go about implementing a custom record backend? > We could really do with some docs on this :-) > > Cheers, Tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
