The railtie sets ::Sequel::Model.raise_on_save_failure = false (in config.after_initialize block at sequel-rails/railtie), but except for development environment the models are already loaded at this stage, thus all the models have raise_on_save_failure set to true.

With ActiveRecord missing, the transactional_fixtures feature must be disabled, but this has the side-effect of turning off transactions for unit tests.

I've searched for a method to re-engage this with no luck, so as an alternative I've created a quick work-around that wraps the test runner in a transaction that's rolled back:

http://gist.github.com/515753

The provided rake tasks 'db:create' and 'db:drop' are created like:

task :create, :env, :needs => :environment do |t, args|
  args.with_defaults(:env => Rails.env)
...

, which ends up args = {:env => "/Users/pota/.bashrc"} on my machine, which is obviously not what it should be (Rails.env is "test", but the bashrc is set so it simply does not overwrite it). (Mac OS X 10.6.6., ruby 1.8.7.)

I'm getting 5 warnings like the following when upgraded to rails 3.0.11 gems:

WARNING: 'task :t, arg, :needs => [deps]' is deprecated. Please use 'task :t, [args] => [deps]' instead.
at /opt/local/lib/ruby/gems/1.8/gems/sequel-rails-0.1.8/lib/sequel-rails/railties/database.rake:15

The command "sudo gem install sequel-rails" produces the following error:

ERROR: Error installing sequel-rails:
activemodel requires activesupport (= 3.0.0.rc2, runtime)

I'm sure this is because Rails 3.0 final is out today.

When I try to run either db:reset or db:setup, rake complaints about "undefined method '[]' for nil:NilClass", which I believe is that rake calls db:drop instead of db:drop:all.

As I can see, the project is unmaintained since two years.

We are using a forked and patched version of sequel-rails in production and maintaining our own sequel-rails for this purpose (https://github.com/iblue/sequel-rails/tree/production). If you do not want to maintain your version anymore, I would like to take over this project.

Now that Rails 3 has been released and 3.1 is around the corner, any chance of releasing a new version with updated dependencies?

schema:dump needs to include the migration version in schema.rb

schema:load needs to add migration records assuming that all migrations up to the indicated version were applied.