Start testing ruby 2.1.0 and rbx-2 on travis
Remove deprecation warning for odbc adapter :driver option

Ross Attrill has stated that the option does work correctly,
so there is no reason to deprecate or remove it.
Remove some pointless spec code from validation helpers spec
Support :dataset option to validates_unique vaildation

This is useful any time the model uses a filtered dataset, but
the database has a unique index on the entire table.
Make auto_validations uniqueness validations work correctly for STI subclasses

STI subclasses use a filtered dataset, but the parsed index will be
for an unfiltered dataset, so make sure to use the unfiltered
dataset when setting up the uniqueness validation.
Add update_or_create plugin, for updating an object if it exists, or creating such an object if it does not

This has been requested by a few people recently, and looking
back at GitHub issues, there were a few related to this that
I forgot about, so it seems like a good idea to have this as
one of the officially supported plugins.
Support rolling back transactions in killed threads in Ruby 2.0+.
Delete one version of commit_or_rollback_transaction, since the other works for either case.
Update changelog for last commit
Syntax error in closing tag
List :name as option for DB.add_index
Pass opts[:schema] through to jdbc getTables method
Minor tweak for jdbc Database#tables commit, and update CHANGELOG

:schema should be allowed to be specified as a symbol, as it is
on other adapters.
Make SQLTime#to_s return a string in HH:MM:SS format, since it shouldn't include date information
Add example for a `rake db:migrate` task.
Merge branch 'rake-migrate-docs' of git://github.com/avdi/sequel
Add spec for one_to_one :validate option usage in setter
Support :raise_on_save_failure option for one_to_many associations

Previously, the add/remove association methods for one_to_many
associations explicitly raised exceptions even if the save method
returned false (because the associated object used
raise_on_save_failure = false).  One reason for that is that the
add/remove methods unconditionally added the object to the cached
association and ran callbacks, since the internal _add/_remove
method return values were not inspected.

Change the add/remove methods to return if the _add/_remove methods
return nil/false and :raise_on_save_failure is false.
Support :raise_on_save_failure option for pg_array_to_many and many_to_pg_array associations
Remove mention of after_initialize from instance_hooks

It's no longer a default hook, so there is no reason to reference it.