Make Dataset#insert work on PostgreSQL if the table name is a SQL::PlaceholderLiteralString (Fixes #736)
Remove usage of Rubyforge (Fixes #734)

Switch to hosting the website at sequel.jeremyevans.net.
Remove some unnecessary code from Rakefile
Add support for :on_commit in create_table for postgres adapter
Minor changes for previous commit

Test for behavior, not specific SQL. Don't test for specific
error messages. Update CHANGELOG.
Update plugins
Fix link in last commit
Fix typo in `Sequel.connect` code example
Add ref on how to add pg_array column

#476
Update pg_array.rb
Update pg_hstore.rb
Update pg_* extensions with details on how to use types in CREATE/ALTER table statements
Bump version to 4.5.0
Recognize a couple additional disconnect errors in the jdbc/postgresql adapter (Fixes #742)
Do not attempt and eager load and raise an exception when doing Model.eager(...).naked.all

In this case, you can't eager load because you don't have a model
object, so just skip eager loading.
Host blog on Sequel's GitHub Pages website instead of Heroku

This is more to get away from the toto-based blog.  As Sequel
already uses GitHub pages to host the main site, and that uses
jekyll which is blog aware, it made sense to import the toto
based site into Sequel's main site.
Support :server option for Database#{commit,rollback}_prepared_transaction on PostgreSQL, MySQL, and H2 (Fixes #743)
Support OFFSET/FETCH for ordered datasets on Microsoft SQL Server 2012

Microsoft SQL Server 2012 adds native support for offsets, but
support is limited to datasets that have orders, and using it
requires a different limit syntax than TOP.  While it has limitations,
most people using offsets are going to be using them with limits
and orders, so it handles most actual use cases.

This changes Sequel to use the new offset syntax on SQL Server 2012
for ordered queries, instead of emulating offsets with a subquery
using row_number.
Don't use a subselect when using offset for unordered datasets on MSSQL 2012+

This extends the previous commit to not use a subselect even in
the unordered case.  Since Sequel's offset emulation via row number
requires adding an order anyway on MSSQL, this should just eliminate
the subquery.

There is a slight difference, in that because the order is being
specifed in the ORDER BY clause instead of the over clause, we can
just order by the first column instead of having to get the column
names (which can cause problems if aliases are used).  This should
cause no problems in practice, since if the user did not specify
an order, the database is free to return results in an arbitrary
order.
Add an integration test for ordering by column position