README.md in sequel-rails-0.9.17 vs README.md in sequel-rails-1.0.0
- old
+ new
@@ -8,11 +8,11 @@
[travis]: http://travis-ci.org/TalentBox/sequel-rails
[codeclimate]: https://codeclimate.com/github/TalentBox/sequel-rails
This gem provides the railtie that allows
[sequel](http://github.com/jeremyevans/sequel) to hook into
-[Rails (3.x, 4.x and 5.x)](http://github.com/rails/rails) and thus behave like a
+[Rails (4.x and 5.x)](http://github.com/rails/rails) and thus behave like a
rails framework component. Just like activerecord does in rails,
[sequel-rails](http://github.com/talentbox/sequel-rails) uses the railtie API to
hook into rails. The two are actually hooked into rails almost identically.
The code for this gem was initially taken from the excellent
@@ -26,12 +26,11 @@
[brasten](https://github.com/brasten) proposed us.
Using sequel-rails
==================
-Using sequel with Rails (3.x, 4.x or 5.x) requires a couple minor
-changes.
+Using sequel with Rails (4.x or 5.x) requires a couple minor changes.
First, add the following to your Gemfile (after the `Rails` lines):
```ruby
# depending on you database
@@ -58,11 +57,11 @@
require "action_controller/railtie"
require "action_mailer/railtie"
require "action_view/railtie"
require "action_cable/engine"
require "sprockets/railtie"
-require "rails/test_unit/railtie
+require "rails/test_unit/railtie"
```
Then you need to get rid of `ActiveRecord` configurations, that is if you
didn't generate the new app with `-O` (or the long form `--skip-active-record`):
@@ -396,10 +395,13 @@
* Lukas Fittl (@lfittl)
* Jordan Owens (@jkowens)
* Pablo Herrero (@pabloh)
* Henre Botha (@henrebotha)
* Mohammad Satrio (@tyok)
+* Gencer W. Genç (@gencer)
* Steve Hoeksema (@steveh)
+* Jester (@Jesterovskiy)
+* ckoenig (@ckoenig)
Credits
=======
The [dm-rails](http://github.com/datamapper/dm-rails) team wrote most of the original code, I just sequel-ized it, but since then most of it has been either adapted or rewritten.