+1. Any given persistence provider back-end (like yo say, LDAP, JPA etc) should be required to implement these as part of there implementation. I don't think they should have a default behavior however...
Now wanting to open another pandora's box, but out of interest, how will the validation stuff tie into the Record? Sounds like things are moving on swimmingly. Great work guys! Cheers, Tim On 3 Nov 2008, at 13:33, Marius wrote: > Derek, they are separated. Record itself has no idea about DB. > Nevertheless save/update/delete semantic applies for any possible > backend (LDAP, JDO, RDBMS ... you name it). So I wonder if save/ > delete/ > update should exist in Record as "dummy" or as they are today only on > DBRecord. Personally I prefer them the way they are today (in > DBRecord) ... but other people may feel different so I'm opened for > valid arguments. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
