technically rails 2 was already supported, but you would get lots of ugly deprecation warnings
updated rake task for Ruby 2.0 compatibility
Gem.searcher is deprecated, so I updated the rake task to use Gem::Specification.find_all_by_name instead.
update ruby_parser dependency
and allow ruby 1.9 syntax parsing using the support in ruby_parser 3.x
* some rails 3.1+ groundwork * get rid of jeweler * load up models the rails-y way if we can * start cleaning up hair_trigger.rb
Only include first event for sqlite trigger
now if the trigger body is a hash rather than a string, you can specify different sql for different databases. supported keys include :mysql/ :sqlite/:postgresql/:default. this is useful for scenarios where one database needs a slightly different trigger due to syntax or performance reasons.
use the migration-provided connection, rather than ActiveRecord::Base
we no longer run each migration in noop mode to get at the triggers (using an AR::Migration monkey-patch)... this was uber-dangerous since we only intercepted things that fell through to the connection (e.g. create_table or execute), and not other stuff (e.g. Foo.update_all or MyWebService.call). we now use ruby_parser to extract triggers (or in the case of schema.rb, just a simple regex) added some little regex checks to model and migration loading so that we don't bother loading or parsing classes that have no triggers