On Feb 5, 10:33 pm, Jeremy Evans <[email protected]> wrote:
> On Feb 5, 7:25 pm, "Skye sh...@#$" <[email protected]> wrote:
>
> > DB = Sequel.odbc('md', :user => 'qwert12345', :password => '123...@#$
> > %')
>
> Include the :db_type=>'mssql' option in the above call. Also, you may
> want to do possibly one or more of the following:
>
> DB.identifier_input_method = nil
> DB.identifier_output_method = nil
> DB.quote_identifiers = false
Thanks, that did it.
As for the identifier_{input,output}_methods, Is there a reason why
they're applied to table names?
I'd think the most common use case for these methods are with models,
turning a column's name into to something that follows Ruby's method
naming convention.
In some cases, since the table name is transformed, these methods
aren't as useful as they could be -for Models:
DB.identifier_input_method = :camelize
DB.identifier_output_method = :underscore
class Blog < Sequel::Model(:CRAP_BLOG)
set_primary_key :identifier
end
-Skye
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sequel-talk?hl=en.
