On Mar 5, 4:51 pm, Jeremy Evans <[email protected]> wrote: > Well, not with the alias (this isn't Rails), but I'd be open to a > patch that had save! use a database transaction. I recommend using > database triggers instead of hooks to handle data integrity issues, > but that's not always possible.
Yep, the alias was just what I'm using for now to work ontop of the 2.10.0 gem. I'll make a patch for the latest version on github, cheers. Re triggers - good point, although as you say not always possible, at least (for some of our use cases) not unless we really head a long way down the wormhole of using views, stored procedures etc to implement a lot of our domain logic. -Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
