Re: Sequel not upcase'ing column names when using `rename_column`

2018-02-06 Thread Jeremy Evans
On Sunday, February 4, 2018 at 9:01:18 PM UTC-8, Tom Wardrop wrote: > > Ok, that all makes sense at least. Cheers. > >From some additional research, at least by default, identifiers are case insensitive on Microsoft SQL Server. It it possible to change that by modifying the database's

Re: Sequel not upcase'ing column names when using `rename_column`

2018-02-04 Thread Tom Wardrop
Ok, that all makes sense at least. Cheers. On Monday, 5 February 2018 14:51:47 UTC+10, Jeremy Evans wrote: > > On Sunday, February 4, 2018 at 5:32:47 PM UTC-8, Tom Wardrop wrote: >> >> Not sure if this a bug, but check the following: >> >> # Adds column "TEST" to "RESOURCE" table. >> add_column

Re: Sequel not upcase'ing column names when using `rename_column`

2018-02-04 Thread Jeremy Evans
On Sunday, February 4, 2018 at 5:32:47 PM UTC-8, Tom Wardrop wrote: > > Not sure if this a bug, but check the following: > > # Adds column "TEST" to "RESOURCE" table. > add_column :resource, :test, :bit > > # Renames "TEST" to "another_test" in lower case > rename_column :resource, :test,

Sequel not upcase'ing column names when using `rename_column`

2018-02-04 Thread Tom Wardrop
Not sure if this a bug, but check the following: # Adds column "TEST" to "RESOURCE" table. add_column :resource, :test, :bit # Renames "TEST" to "another_test" in lower case rename_column :resource, :test, :another_test This is using the TinyTDS adapter. Adding columns automatically converts