Then how to go back from the case class (pulled in from memcached) to a Mapper object (that I can modify and then save)? I'm worried about getting the mapper object in an incorrect state where it thinks it needs to add a new row to the table on save rather than update an existing one.
Ideally I'd like to override findDbByKey() in my MetaMapper class, and save() in my Mapper class(1) and leave the rest of my code unchanged. -harryh (1) And maybe also bulkDelete_!! and delete, but you get the general idea. > Personally, I'd use final case classes, serialize them via lift-json and put > them in memcached... but that's just me. -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@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=.
