A single adapter for ActiveRecord makes all this possible. Some other ideas are floating
around about how to extend Rails in other Java-specific ways. Some of the more interesting
proposals concern making a Hibernate back end for Rails. If someone would do this, it would
open up the Rails world to a completely new type of application, which until now has been
difficult or impossible to accomplish due to Rails??™ opinionated way of doing things.
It??™s also possible to use AR-JDBC outside of Rails. For testing purposes, where it is interesting
to talk directly to a database and watch what happens, a deployment with only ActiveRecord and
AR-JDBC makes sense, especially because in many cases it??™s much easier to get a strange database
working with JDBC than with C drivers.
Supported Databases
As mentioned before, AR-JDBC supports many databases out of the box. This section will
walk through each of them, giving a little information about what??™s needed to get the database
configuration set up in a way that will work with that database. The sections won??™t show how
to set up the databases themselves, just how to configure Rails for them. The example configuration
will be the development section of config/database.yml, and in most cases will use the
localhost, with a database name of ar_test, a username of ???ar_user,??? and a password of
???ar_pass.??? Any deviations from this will be noted at the point they happen.
MySQL
The MySQL support in AR-JDBC is one of the more stable parts.
Pages:
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173