This isn't related to syntax, but: I've been using these statements to do permission checks. For example, to check that a user has permission to create a specific object record before it gets inserted. I'm currently depending on the atomic nature of the .flush operation, such that if the user doesn't have permission to do even one part of what the .flush entails, none of it goes through. However, for non-transactional databases (isam) this functionality breaks, right?
Are before_* callbacks run for all objects to be flushed that have them before any sql is run? Or is it a for object in to_flush: object.before_*; object.save construct? ~jon On Jul 30, 2:07 pm, Jonathan LaCour <[EMAIL PROTECTED]> wrote: > Gaetan de Menten wrote: > > As I already said, I like the idea of decorators. I don't think the > > responds_to_events is a good idea though. The decorators should be > > able to register themselves. It seems pretty logical that if you > > decorate some methods with event callbacks, you want them to be used. > > I'll see if I can make it work without the extra statement. I am > with you in principle, but am not sure how I will be able to make the > decorator do what we want without hacking into Elixir's core. We'll > need to add a MapperExtension and I am not sure that the decorator will > have access to what it needs at the time that it is called, but we'll > see. > > I'll report back later on tonight or tomorrow! > > -- > Jonathan LaCourhttp://cleverdevil.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" 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/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
