aboutsummaryrefslogtreecommitdiffstats
path: root/ci
diff options
context:
space:
mode:
authorAlfred Wong <alfiewong@gmail.com>2012-06-17 11:43:31 -0400
committerBen Woosley <ben.woosley@gmail.com>2013-07-22 04:39:35 -0700
commit39b5bfe2394d0a4d479b41ee8d170e0f6c65fd59 (patch)
treec8118d50c862e25505698b00327acad09d922e2c /ci
parentbf2161d1abf2d8aa09a7cc36b72cf0da7f6e167c (diff)
downloadrails-39b5bfe2394d0a4d479b41ee8d170e0f6c65fd59.tar.gz
rails-39b5bfe2394d0a4d479b41ee8d170e0f6c65fd59.tar.bz2
rails-39b5bfe2394d0a4d479b41ee8d170e0f6c65fd59.zip
Specified column type for quote_value
When calling quote_value the underlying connection sometimes requires more information about the column to properly return the correct quoted value. I ran into this issue when using optimistic locking in JRuby and the activerecord-jdbcmssql-adapter. In SQLSever 2000, we aren't allowed to insert a integer into a NVARCHAR column type so we need to format it as N'3' if we want to insert into the NVARCHAR type. Unfortuantely, without the column type being passed the connection adapter cannot properly return the correct quote value because it doesn't know to return N'3' or '3'. This patch is fairly straight forward where it just passes in the column type into the quote_value, as it already has the ability to take in the column, so it can properly handle at the connection level. I've added the tests required to make sure that the quote_value method is being passed the column type so that the underlying connection can determine how to quote the value.
Diffstat (limited to 'ci')
0 files changed, 0 insertions, 0 deletions