On Feb 9, 4:33 pm, "Skye sh...@#$" <[email protected]> wrote: > As for the identifier_{input,output}_methods, Is there a reason why > they're applied to table names?
Tables are identifiers, just as columns are. Also, in Sequel, there's not a way to tell if an identifier will be used as a table or a column. > 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 Actually, the main use so far as I know has just been downcasing when retrieving and upcasing before inputting, but camelize/underscore should work fine, assuming that fits with your schema. Jeremy -- 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.
