You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Initial IronRuby ADONET connection mode support baked right in. Removed most &block parameters, no handle/request object yielded anymore. Better abstraction and compliance per the ActiveRecord abstract adapter to not yielding handles for #execute and only for low level #select. Better wrapping of all queries at lowest level in #log so exceptions at anytime can be handled correctly by core AR. Critical for System::Data's command readers. Better abstraction for introspecting on #connection_mode. Added support for running singular test cases via TextMate's Command-R.
Copy file name to clipboardExpand all lines: README.rdoc
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,8 @@ The SQL Server adapter for rails is back for ActiveRecord 2.2 and up! We are cur
6
6
7
7
== What's New
8
8
9
-
* Strict ODBC required! No DBI means around 20% faster!
9
+
* IronRuby support using ADONET connection mode.
10
+
* Direct ODBC mode. No DBI anymore, means around 20% faster!
10
11
* Now supports SQL Server 2008 too!
11
12
* Fully tested under 1.9!!! Correctly encodes/decodes UTF-8 types in ruby 1.9 too.
12
13
* Now supports both rails 2.2 & 2.3!!!
@@ -129,7 +130,7 @@ It is our goal to match the adapter version with each version of rails. However
129
130
130
131
== Installation
131
132
132
-
You will need Ruby ODBC. If you are using the adapter under 1.9, then you need at least ruby-odbc version 0.9996. Currently ADO modes are not supported since we dropped the unnecessary DBI dependency and transport layer. This was done so we could incorporate other transports such as ADO.NET (w IronRuby) mode in the future or possibly a straight FreeTDS layer. The sky is the limit now and we have a code that can be accept these optional transports. If you are interested in helping, open a ticket and submit a patch. Or start a conversation on the Google Group.
133
+
You will need Ruby ODBC. If you are using the adapter under 1.9, then you need at least ruby-odbc version 0.9996. ODBC is the preferred mode, however if you are using IronRuby you can use the ADONET connection mode which uses native System.Data connection. Other connection modes may be supported, possibly a straight FreeTDS layer. The sky is the limit now and we have a code that can be accept these optional transports. If you are interested in helping, open a ticket and submit a patch. Or start a conversation on the Google Group.
133
134
134
135
$ gem install activerecord-sqlserver-adapter
135
136
@@ -142,6 +143,15 @@ Here are some external links for libraries and/or tutorials on how to install an
142
143
* http://www.ch-werner.de/rubyodbc/
143
144
144
145
146
+
== IronRuby ADONET Mode
147
+
148
+
A few details on this implementation. All that is needed in your database.yml configuration file is "mode: adonet" vs "odbc" and if you are running IronRuby, the connection will be native. No need for ANY DBI middle layer is needed or special extension to this adapter. The adapter is opinionated in regards to IronRuby on types coming out of the DB. For example strings will be String, not System::String and DateTime vs System::Datetime. This is so that we can pass all the ActiveRecord tests. When using the adapter it is best to stick with default Ruby types coming in and out. Currently IronRuby is passing most of the ActiveRecord tests. Here is a list of the ones remaining.
149
+
150
+
http://gist.github.com/381101
151
+
152
+
Some are in the adapters realm and some are in Marshalling which is IronRuby core to fix. Feel like helping knock these out, submit a patch.
153
+
154
+
145
155
== Contributing
146
156
147
157
If you’d like to contribute a feature or bugfix, thanks! To make sure your fix/feature has a high chance of being added, please read the following guidelines. First, ask on the Google list, IRC, or post a ticket on github issues. Second, make sure there are tests! We will not accept any patch that is not tested. Please read the RUNNING_UNIT_TESTS file for the details of how to run the unit tests.
0 commit comments