In my comprehension of the overall framework, Mapper provides persistence together with form management for ui construction and some serialization method to support the development of REST services. In the design of Record, persistency has been stripped away in order to create the condition to plug different backend (despite the many DBxxxx polluting the package). in Mapper Schemifier provide initialization service for a persistence layer and hence in the new architecture it should be provided by the specific backend (if required). I am writing a JCR persistence layer and at the moment (addressing jsr-170) I have no need of a Schemifier. In the next version addresing jsr-283 and a proper management of Node types, inside the equivalent of Schemifier I will put the verification if the current repository has the right node types, corresponding to the MetaRecord (extended with JCRNodeType) objects defined by the domain model.
On 29 Lug, 08:40, "marius d." <[email protected]> wrote: > Nope. Record currently has nothing to do with RDBMS. It is a higher > level of model abstraction that allows various implementations. RDBMS > will likely be implemented but likely other models as well such > Cassandra and ZooKeeper thru Dave's GoatRodeo. > > Br's, > Marius > > On Jul 29, 9:16 am, Heiko Seeberger <[email protected]> > wrote: > > > Hi, > > Is there something like Schemifier for lift-record? > > > Heiko > > > -- > > > My blog: heikoseeberger.name > > Follow me: twitter.com/hseeberger > > OSGi on Scala:www.scalamodules.org > > Lift, the simply functional web framework: liftweb.net --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
