…ub selects to be used. Resolves ticket #11
…:test_sqlserver_odbc. Resolves ticket #10 [Ken Collins]
…atted, or long winded user defined functions, for default values. Resolves ticket #8
…to Bignum as expected.
…sses through any scoped :order parameters. We need these so that our limit and offset code can properly reverse and re-order the inner query and thus correctly paginate the results. Signed-off-by: Murray Steele <firstname.lastname@example.org>
…der SQL Server 2005 to be a :text type. This ensures schema dumper does the right thing. Fixes ticket #30.
…ock option is present. Added tests to make sure tally SQL is augmented correctly and tests to make sure that add_lock! is doing what it needs for deep sub selects in paginated results.
… method does the connect and return active? all in one.
…. By default each query run through the adapter will automatically reconnect at standard intervals, logging attempts along the way, till success or the original exception bubbles up. See docs for more details. Resolves ticket #18 http://rails-sqlserver.lighthouseapp.com/projects/20277/tickets/18-sql-server-adapter-doesnt-reconnect-on-lost-connection
…der clause like "description desc". This resolves ticket #26 http://rails-sqlserver.lighthouseapp.com/projects/20277/tickets/26-cant-have-a-description-column-and-sort-desc
…ng #run_with_isolation_level method that can take a block or not. Also implement a #user_options method that reflects on the current user session values. Resolves #20 [Murray Steele]
…rious isolation levels (e.g. to go around other processes locking tables).
…lements in the statement. This could be eager loaded associations, joins, etc. Done so that paginated results can easily add lock options for performance. Note, the tally count in add_limit_offset! use "WITH (NOLOCK)" explicitly as it can not hurt and is needed.