On Sep 12, 2008, at 6:53 PM, Jeremy Evans wrote: >>> In the absence of an AS clause, SQLite makes no promises about >>> column >>> names. If you want a specific column name, use an AS clause on that >>> column to specify the name. Otherwise, you get what you get and >>> what >>> you get might change from one point release to the next. (That >>> said, >>> people tend to scream furiously when the column naming rules >>> changes, >>> so we do try to avoid changing them without a very good reason.) >> >> -http://article.gmane.org/gmane.comp.db.sqlite.general/41090 > > SQLite may not consider it a bug, but I do, as no sane database should > operate that way. That said, I'd be willing to consider a patch for > the SQLite adapter that used AS for regular columns.
After sufficient discussion, it was viewed as a bug and a patch has already been checked-in. [1] I'll peek into the patch idea, though, so Sequel will work as (I) expected for older installs of SQLite. Give me a hint. Am I correct in thinking that it will involve code in one of the sqlite.rb files, code which will supersede the definition of select_sql in sql_core/dataset/sql.rb in a way that changes the return value of column_list, but only for specific columns in the set? Or perhaps just a custom implementation of column_list? (I've not yet seen where all that is used.) Yak shaving, ho! [1] http://www.sqlite.org/cvstrac/chngview?cn=5696 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
