On 21 Feb 2007, at 14:40, John Siracusa wrote: [snip] > That's reasonable. I've done similar things in generated and manually > created classes. [snip]
Super :) > >> As I understand it triggers happen after the object is updated in >> memory. I >> want to shim stuff in before this (so I can preserve the original >> value if I >> don't want the update to proceed) > > You're right that the on_set trigger happens after the column value > has been set. I could probably stand to add a few more trigger events > (e.g., before_set) but I'm wary of trigger-itis gumming up the works. > So I've just been waiting to see what kinds of events people actually > need. It seems like you're registering one vote for before_set :) > But in the meantime, the technique you're using instead is fine. ++ for before_set :-) Cheers, Adrian PS And thanks for R:D:O - it keeps exceeding my expectations. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
