Another
thing that usually differs between different database vendors is how quoting of strings and
other database types is handled. This typically needs to be changed in both the Column and
the Adapter, but once again the existing adapters display many ways of doing this.
Of course, the current set of databases is just what is known at the time of writing. It??™s
possible that the amount of databases supported has been extended at the time you??™re reading
this. The only way to make sure is to check the documentation for AR-JDBC.
Summary
We??™ve walked through the rest of the Shoplet application, and you??™ve seen how to simplify
browsing for the user, while still not having to duplicate code to manage a menu. We??™ve also
looked more at how to test models and functionality with Rails??™ built-in testing support.
I couldn??™t show all testing that should have been done, but I hope what was covered was
enough to whet your appetite enough to research more testing by yourself.
The second half of the chapter looked at AR-JDBC a little more closely. It delved into the
different databases supported, how you should configure them, and also what you can do if
you need to use a database that isn??™t supported by AR-JDBC yet.
The purpose of the preceding chapters has been mainly to introduce you to how Rails
works, and to some of the quirks that come up in conjunction with JRuby. You should know
now how to handle the day-to-day tasks of building a simple application in JRuby on Rails.
Pages:
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180