artpop-2000-2005-adapter 2.2.15

data/CHANGELOG

@@ -0,0 +1,142 @@
+
+MASTER
+
+* 
+
+
+* 2.2.15 * (March 23rd, 2009)
+
+* Better add_lock! method that can add the lock to just about all the elements 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. [Ken Collins]
+
+
+* 2.2.14 * (March 17th, 2009)
+
+* Rails2.3 - Back passing tests on 2.2 work. Includes: (1) Created new test helpers that check ActiveRecord 
+  version strings so we can conditionally run 2.2 and 2.3 tests. (2) Making TransactionTestSqlserver use Ship vs 
+  Bird model. Also made it conditional run a few blocks for different versions of ActiveRecord. (3) Previous 
+  JoinDependency#aliased_table_name_for is now only patched in ActiveRecord equal or greater than 2.3. [Ken Collins]
+
+* Rails2.3 - Implement new savepoint support [Ken Collins]
+  http://rails.lighthouseapp.com/projects/8994/tickets/383
+  http://www.codeproject.com/KB/database/sqlservertransactions.aspx
+
+* Rails2.3 - Coerce NestedScopingTest#test_merged_scoped_find to use correct regexp for adapter. [Ken Collins]
+
+* Rails2.3 - Implement a custom ActiveRecord::Associations::ClassMethods::JoinDependency::JoinAssociation#aliased_table_name_for
+  method that uses a Regexp.escape so that table/column quoting does not get ignored. [Ken Collins]
+
+* Rails2.3 - Implement #outside_transaction? and a new transaction test case to test some SQL Server 
+  basic support while implementing this method. Future home of some savepoint tests too. [Ken Collins]
+
+* Rails2.3 - Coerced tests that ensure hash conditions on referenced tables are considered when eager 
+  loading with limit/offset. Information on these changes and the ticket in rails are.
+  http://github.com/rails/rails/commit/9a4d557713acb0fc8e80f61af18094034aca029a
+  http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1404-conditions_tables-doesnt-understand-condition-hashes
+
+* Rails2.3 - Add coerced tests for true/false attributes in selects use SQL Server case statement. [Ken Collins]
+
+* Making sure that smalldatetime types are OK to use. Also fixed a bug in the #view_information method that 
+  checks to see if a view definition is equal to 4000 chars, meaning that it is most likely truncated and 
+  needs to use the backup method of sp_helptext to get it's view definition. [Ken Collins]
+
+
+* 2.2.13 * (February 10th, 2009)
+
+* Update #indexes to use unqualified table name. Fixes cases where users may decide to use table 
+  name prefixes like 'dbo.'. [Ken Collins]
+
+
+* 2.2.12 * (February 8th, 2009)
+
+* Update table_exists? to work with qualified table names that may include an user prefix. [Ken Collins]
+
+
+* 2.2.10/11 * (January 22nd, 2009)
+
+* Add a rails-sqlserver-2000-2005-adapter.rb file so that long :lib option for config.gem is no longer needed.
+
+
+* 2.2.9 * (January 22nd, 2009)
+
+* Fixing a small bug in the deprecated DBI::Timestamp conversion so it correctly converts nanosecond whole 
+  numbers to back to pre type cast SQL Server milliseconds, ultimately allow ruby's Time#usec which is 
+  microseconds to be correct. [Ken Collins]
+  
+* Sometimes views are more than 4000 chars long and will return NULL for the VIEW_DEFINITION. If so, use 
+  sp_helptext procedure as a backup method. [Ken Collins]
+
+
+* 2.2.8 (January 9th, 2009)
+
+* Update execute_procedure method a bit to remove excess code. [Ken Collins]
+
+
+* 2.2.7 (January 9th, 2009)
+
+* Created a connection#execute_procedure method that takes can take any number of ruby objects as variables 
+  and quotes them according to the connection's rules. Also added an ActiveRecord::Base class level core 
+  extension that hooks into this. It also checks if the connection responds to #execute_procedure and if 
+  not returns an empty array. [Ken Collins]
+
+* Added a #enable_default_unicode_types class attribute access to make all new added or changed string types 
+  like :string/:text default to unicode/national data types. See the README for full details. Added a rake 
+  task that assists setting this to true when running tests.  [Ken Collins]
+
+
+* 2.2.6 (January 8th, 2009)
+
+* Introduced a bug in 2.2.5 in the #add_order! core ext for ActiveRecord. Fixed [Ken Collins]
+
+
+* 2.2.5 (January 4th, 2009)
+
+* Added a log_info_schema_queries class attribute and make all queries to INFORMATION_SCHEMA silent by 
+  default. [Ken Collins]
+
+* Fix millisecond support in datetime columns. ODBC::Timestamp incorrectly takes SQL Server milliseconds
+  and applies them as nanoseconds. We cope with this at the DBI layer by using SQLServerDBI::Type::SqlserverTimestamp 
+  class to parse the before type cast value appropriately. Also update the adapters #quoted_date method 
+  to work more simply by converting ruby's #usec milliseconds to SQL Server microseconds. [Ken Collins]
+
+* Core extensions for ActiveRecord now reflect on the connection before doing SQL Server things. Now 
+  this adapter is compatible for using with other adapters. [Ken Collins]
+
+
+* 2.2.4 (December 5th, 2008)
+
+* Fix a type left in #views_real_column_name. Also cache #view_information lookups. [Ken Collins]
+
+
+* 2.2.3 (December 5th, 2008)
+
+* Changing back to using real table name in column_definitions. Makes sure views get back only the columns 
+  that are defined for them with correct names, etc. Now supporting views by looking for NULL default and 
+  then if table name is a view, perform a targeted with sub select to the real table name and column name 
+  to find true default. [Ken Collins]
+
+* Ensure that add_limit_offset! does not alter sub queries. [Erik Bryn]
+
+
+2.2.2 (December 2nd, 2008)
+
+* Add support for view defaults by making column_definitions use real table name for schema info. [Ken Collins]
+
+* Include version in connection method and inspection. [Ken Collins]
+
+
+2.2.1 (November 25th, 2008)
+
+* Add identity insert support for views. Cache #views so that identity #table_name_or_views_table_name 
+  will run quickly. [Ken Collins]
+
+* Add views support. ActiveRecord classes can use views. The connection now has a #views method and 
+  #table_exists? will now fall back to checking views too. [Ken Collins]
+
+
+2.2.0 (November 21st, 2008)
+
+* Release for rails 2.2.2. Many many changes.  [Ken Collins], [Murray Steele], [Shawn Balestracci], [Joe Rafaniello]
+

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2008 
+ 
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+ 
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+ 
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.rdoc

@@ -0,0 +1,157 @@
+
+== Rails SQL Server 2000 & 2005 Adapter
+
+The SQL Server adapter for rails is back for ActiveRecord 2.2 and up! We are currently passing all tests and hope to continue to do so moving forward. 
+
+
+== What's New
+
+* Now supports both rails 2.2 & 2.3!!!
+* An ActiveRecord::Base.execute_procedure method that can be used by classes.
+* Enabled support for DDL transactions.
+* Micro second support. Time#usec is automatically converted to SQL Server's 3.33 millisecond limitation.
+* Datetime data types before type casting are represented correctly. For example: 1998-01-01 23:59:59.997
+* Implementation for #disable_referential_integrity used by ActiveRecord's Fixtures class.
+* Pessimistic locking suppot. See the #add_lock! method for details.
+* Enabled #case_sensitive_equality_operator used by unique validations.
+* Unicode character support for nchar, nvarchar and ntext data types. Configuration option for defaulting all string data types to the unicode safe types.
+* View support for table names, identity inserts, and column defaults.
+
+==== Date/Time Data Type Hinting
+
+Both SQL Server 2000 and 2005 do not have native data types for just 'date' or 'time', it only has 'datetime'. To pass the ActiveRecord tests we implemented two simple class methods that can teach your models to coerce column information to be cast correctly. Simply past a list of symbols to either the <tt>coerce_sqlserver_date</tt> or <tt>coerce_sqlserver_time</tt> methods that correspond to 'datetime' columns that need to be cast correctly.
+
+  class Topic < ActiveRecord::Base
+    coerce_sqlserver_date :last_read
+    coerce_sqlserver_time :bonus_time
+  end
+
+This implementation has some limitations. To date we can only coerce date/time types for models that conform to the expected ActiveRecord class to table naming convention. So a table of 'foo_bar_widgets' will look for coerced types in the FooBarWidget class if it exists.
+
+==== Executing Stored Procedures
+
+Every class that sub classes ActiveRecord::Base will now have an execute_procedure class method to use. This method takes the name of the stored procedure which can be a string or symbol and any number of variables to pass to the procedure. Arguments will automatically be quoted per the connection's standards as normal. For example.
+
+  Account.execute_procedure :update_totals, 'admin', nil, true
+
+==== Native Data Type Support
+
+Currently the following custom data types have been tested for schema definitions.
+
+* char
+* nchar
+* nvarchar
+* ntext
+* varchar(max) for SQL Server 2005 only.
+* nvarchar(max) for SQL Server 2005 only.
+
+For example:
+
+  create_table :sql_server_custom_types, :force => true do |t|
+    t.column :ten_code,       :char,      :limit => 10
+    t.column :ten_code_utf8,  :nchar,     :limit => 10
+    t.column :title_utf8,     :nvarchar
+    t.column :body,           :varchar_max    # Creates varchar(max)
+    t.column :body_utf8,      :ntext
+    t.column :body2_utf8,     :nvarchar_max   # Creates nvarchar(max)
+  end
+
+Manually creating a varchar(max) on SQL Server 2005 is not necessary since this is the default type created when specifying a :text field. As time goes on we will be testing other SQL Server specific data types are handled correctly when created in a migration.
+
+
+==== Native Text/String/Binary Data Type Accessor
+
+To pass the ActiveRecord tests we had to implement an class accessor for the native type created for :text columns. By default any :text column created by migrations will create these native types.
+
+* SQL Server 2000 is 'text'
+* SQL Server 2005 is 'varchar(max)'
+
+During testing this type is set to 'varchar(8000)' for SQL Server 2000. The reason is that rails expects to be able to use SQL = operators on text data types and this is not possible with a native 'text' data type in SQL Server. The default 'varchar(max)' for SQL Server 2005 can be queried using the SQL = operator and has plenty of storage space which is why we made it the default for 2005. If for some reason you want to change the data type created during migrations for any SQL Server version, you can configure this line to your liking in a config/initializers file.
+
+  ActiveRecord::ConnectionAdapters::SQLServerAdapter.native_text_database_type = 'varchar(8000)'
+  
+Also, there is a class attribute setter for the native string database type. This is the same for both SQL Server 2000 and 2005, 'varchar'. However in can be used instead of the #enable_default_unicode_types below for finer grain control over which types you want unicode safe when adding or changing the schema.
+
+  ActiveRecord::ConnectionAdapters::SQLServerAdapter.native_string_database_type = 'nvarchar'
+
+By default any :binary column created by migrations will create these native types
+
+* SQL Server 2000 is 'image'
+* SQL Server 2005 is 'varbinary(max)'
+
+
+====  Setting Unicode Types As Default
+
+By default the adapter will use non-unicode safe data types for :string and :text types when DEFINING or CHANGING the schema. If you choose, you can set the following class attribute in a config/initializers file that will change this behavior. When set to true it has the equivalent meaning as the two lower items. These examples show detail level alternatives to achieve similar effects.
+  
+  ActiveRecord::ConnectionAdapters::SQLServerAdapter.enable_default_unicode_types = true
+  
+  # SQL Server 2000
+  ActiveRecord::ConnectionAdapters::SQLServerAdapter.native_text_database_type = 'ntext'
+  ActiveRecord::ConnectionAdapters::SQLServerAdapter.native_string_database_type = 'nvarchar'
+  
+  # SQL Server 2005
+  ActiveRecord::ConnectionAdapters::SQLServerAdapter.native_text_database_type = 'nvarchar(max)'
+  ActiveRecord::ConnectionAdapters::SQLServerAdapter.native_string_database_type = 'nvarchar'
+
+It is important to remember that unicode types in SQL Server have approximately half the storage capacity as their counter parts. So where a normal string would max out at (8000) a unicode string will top off at (4000).
+
+
+====  Schema Information Logging
+
+By default all queries to the INFORMATION_SCHEMA table is silenced. If you think logging these queries are useful, you can enable it by adding this like to a config/initializers file.
+
+  ActiveRecord::ConnectionAdapters::SQLServerAdapter.log_info_schema_queries = true
+
+
+== Versions
+
+It is our goal to match the adapter version with each version of rails. However we will track our own tiny version independent of ActiveRecord. For example, an adapter version of 2.2.x will work on any 2.2.x version of ActiveRecord. This convention will be used in both the Git tags as well as the Rubygems versioning.
+
+
+== Installation
+
+First, you will need Ruby DBI and Ruby ODBC. To my knowledge the ADO DBD for DBI is no longer supported. The installation below is not a comprehensive walk thru on how to get all the required moving parts like FreeTDS installed and/or configured. It will also assume gem installations of both the dependent libraries and the adapter itself.
+
+It should be noted that this version of the adapter was developed using both the ancient 0.0.23 version of DBI up to the current stable release of 0.4.0. Because later versions of DBI will be changing many things, IT IS HIGHLY RECOMMENDED that you max your install to version 0.4.0 which the examples below show. For the time being we are not supporting DBI versions higher than 0.4.0. The good news is that if you were using a very old DBI with ADO, technically this adapter will still work for you, but be warned your path is getting old and may not be supported for long.
+
+  $ gem install dbi --version 0.4.0
+  $ gem install dbd-odbc --version 0.2.4
+  $ gem install rails-sqlserver-2000-2005-adapter -s http://gems.github.com
+
+Optionally configure your gem dependencies in your rails environment.rb file.
+
+  config.gem 'dbi', :version => '0.4.0'
+  config.gem 'dbd-odbc', :version => '0.2.4', :lib => 'dbd/ODBC'
+  config.gem 'rails-sqlserver-2000-2005-adapter', :source => 'http://gems.github.com'
+
+Here are some external links for libraries and/or tutorials on how to install any other additional components to use this adapter. If you know of a good one that we can include here, just let us know.
+
+* http://ruby-dbi.sourceforge.net/
+* http://www.ch-werner.de/rubyodbc/
+
+
+== Contributing
+
+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 in Lighthouse. 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.
+
+* Lighthouse: http://rails-sqlserver.lighthouseapp.com/projects/20277-sql-server-05-adapter/tickets
+* Google Group: http://groups.google.com/group/rails-sqlserver-adapter
+* IRC Room: #rails-sqlserver on irc.freenode.net
+
+
+== Credits
+
+Many many people have contributed. If you do not see your name here and it should be let us know.
+
+* Ken Collins
+* Murray Steele
+* Shawn Balestracci
+* Joe Rafaniello
+* Tom Ward
+
+
+== License
+
+Copyright © 2008. It is free software, and may be redistributed under the terms specified in the MIT-LICENSE file.
+

data/RUNNING_UNIT_TESTS

@@ -0,0 +1,60 @@
+== Creating the test database
+
+The default names for the test databases are "activerecord_unittest" and 
+"activerecord_unittest2". If you want to use another database name then be sure 
+to update the connection adapter setups you want to test with in 
+test/connections/<your database>/connection.rb. 
+
+
+== Requirements
+
+The following gems need to be installed. Make sure you have gems.github.com as a
+source. http://github.com/blog/97-github-loves-rubygems-1-2
+
+  * gem install thoughtbot-shoulda -s http://gems.github.com
+  * gem install mocha
+
+The tests of this adapter depend on the existence of rails checkout. All the tests
+defined by rails are re-used. For this to work the following directory structure 
+is assumed to exist:
+
+#{RAILS_ROOT}/vendor/plugins/adapters/sqlserver
+#{RAILS_ROOT}/vendor/rails/activerecord/test
+
+Define a user named 'rails' in SQL Server with all privileges granted. Use an empty 
+password for user 'rails', or alternatively use the OSQLPASSWORD environment variable
+which allows you to set a default password for the current session.
+
+Then run "rake create_databases".
+
+
+== Running with Rake
+
+The easiest way to run the unit tests is through Rake. Either run "rake test_sqlserver" 
+or "rake test_sqlserver_odbc". For more information, checkout the full array 
+of rake tasks with "rake -T"
+
+Rake can be found at http://rake.rubyforge.org
+
+
+== Running with Autotest
+
+Using autotest is easy, just run "autotest" and the tests will run continually in the 
+same order as the rake test command. By default autotest will use ODBC connection. If 
+you want to change this you can edit the autotest/sqlserver.rb file and set odbc_mode 
+to false.
+
+Lastly, you can run autotest on just the adapter specific tests with "autotest sqlserver". 
+This will continuously run ONLY the SQL Sever specific behavior tests which are much 
+quicker to run than the entire active record test suite.
+
+
+== Running by hand
+
+Unit tests are located in test directory. If you only want to run a single test suite, 
+you can do so with:
+
+   rake test_sqlserver TEST=base_test.rb
+   
+That'll run the base suite using the SQLServer-Ruby adapter.
+

data/Rakefile

@@ -0,0 +1,52 @@
+require 'rubygems'
+require 'rake'
+require 'rake/testtask'
+
+
+desc 'Create the SQL Server test databases'
+task :create_databases do
+  # Define a user named 'rails' in SQL Server with all privileges granted
+  # Use an empty password for user 'rails', or alternatively use the OSQLPASSWORD environment variable
+  # which allows you to set a default password for the current session.
+  %x( osql -S localhost -U rails -Q "create database activerecord_unittest" -P )
+  %x( osql -S localhost -U rails -Q "create database activerecord_unittest2" -P )
+  %x( osql -S localhost -U rails -d activerecord_unittest -Q "exec sp_grantdbaccess 'rails'" -P )
+  %x( osql -S localhost -U rails -d activerecord_unittest2 -Q "exec sp_grantdbaccess 'rails'" -P ) 
+  %x( osql -S localhost -U rails -d activerecord_unittest -Q "grant BACKUP DATABASE, BACKUP LOG, CREATE DEFAULT, CREATE FUNCTION, CREATE PROCEDURE, CREATE RULE, CREATE TABLE, CREATE VIEW to 'rails';" -P )
+  %x( osql -S localhost -U rails -d activerecord_unittest2 -Q "grant BACKUP DATABASE, BACKUP LOG, CREATE DEFAULT, CREATE FUNCTION, CREATE PROCEDURE, CREATE RULE, CREATE TABLE, CREATE VIEW to 'rails';" -P )
+end
+
+desc 'Drop the SQL Server test databases'
+task :drop_databases do
+  %x( osql -S localhost -U rails -Q "drop database activerecord_unittest" -P )
+  %x( osql -S localhost -U rails -Q "drop database activerecord_unittest2" -P )
+end
+
+desc 'Recreate the SQL Server test databases'
+task :recreate_databases => [:drop_databases, :create_databases]
+
+
+for adapter in %w( sqlserver sqlserver_odbc )
+  
+  Rake::TestTask.new("test_#{adapter}") { |t|
+    t.libs << "test" 
+    t.libs << "test/connections/native_#{adapter}"
+    t.libs << "../../../rails/activerecord/test/"
+    t.test_files = (
+      Dir.glob("test/cases/**/*_test_sqlserver.rb").sort + 
+      Dir.glob("../../../rails/activerecord/test/**/*_test.rb").sort )
+    t.verbose = true
+  }
+
+  namespace adapter do
+    task :test => "test_#{adapter}"
+  end
+  
+end
+
+desc 'Test with unicode types enabled.'
+Rake::TestTask.new(:test_unicode_types) do |t|
+  ENV['ENABLE_DEFAULT_UNICODE_TYPES'] = 'true'
+  test = Rake::Task['test_sqlserver_odbc']
+  test.invoke
+end

data/autotest/discover.rb

@@ -0,0 +1,4 @@
+
+Autotest.add_discovery do
+  ARGV.first || 'railssqlserver'
+end

data/autotest/railssqlserver.rb

@@ -0,0 +1,16 @@
+require 'autotest/sqlserver'
+
+class Autotest::Railssqlserver < Autotest::Sqlserver
+
+  def initialize
+    super
+    self.libs << "#{File::PATH_SEPARATOR}../../../rails/activerecord/test/"
+    self.extra_files = ['../../../rails/activerecord/test/']
+    self.add_mapping %r%../../../rails/activerecord/test/.*/.*_test.rb$% do |filename, _|
+      filename
+    end
+  end
+  
+
+end
+