It seems this kind of code incites the use of database specific SQL all over the place. Moving these default settings in a before_save and extending the connection adapters (in a /lib/adapters_ext/... folder) to get the values seems like a cleaner way. There can also be transactional issues with this kind of code so it should be clearly stated as *exceptional*.
Gaspard On Sat, Feb 14, 2009 at 6:56 AM, ara.t.howard <[email protected]> wrote: > > useful? > > http://drawohara.com/post/78208216/rails-activerecord-defaults-for-rails-2-2-2 > > a @ http://codeforpeople.com/ > -- > we can deny everything, except that we have the possibility of being > better. simply reflect on that. > h.h. the 14th dalai lama > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
