On Nov 23, 12:18 pm, John Firebaugh <[email protected]> wrote: > Use case is library code that wants to force a raise on failure > without changing any permanent state. For example, a "railsify" plugin > that makes sequel models behave more like ActiveRecord models wants to > define a save! method that always raises on failure, while not > perturbing the behavior of save. > > Patch is attached. Most invasive bit is adding an optional opts > argument to valid?, which could break in cases where it was overridden > (as some specs did).
Hmm, I'm on the fence about this. It's more invasive than I'd like, and you could easily handle it by rolling your own instance method that uses an ensure block. Does anyone else have feelings about this patch either way? Jeremy -- 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.
