What are the use cases then? Why Mapper over Record? If the answer is "people are using it and we have to support it", then why would I go down that path. There must have been a reason to create Record over Mapper.
On Jul 11, 11:16 pm, Derek Chen-Becker <[email protected]> wrote: > Mapper will be maintained for quite a while after Record comes out, and the > two (at present) have similar architectures. JPA is certainly an option, but > don't toss Mapper out as an option simply because Record will be in place in > the near future. > > Derek > > On Sat, Jul 11, 2009 at 7:41 AM, czerwonka <[email protected]> wrote: > > > It'd be nice not to have to port. I'd hat to have to port my mapper > > code as soon after I write it. Maybe JPA is the answer then. > > > On Jul 10, 7:24 am, "marius d." <[email protected]> wrote: > > > Mapper as Record is not yet complete. > > > > Br's, > > > Marius > > > > On Jul 10, 4:21 pm, czerwonka <[email protected]> wrote: > > > > > If I'm starting today, should I use Mapper or Record? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
