On Sep 12, 2008, at 10:30 AM, David Lee <[EMAIL PROTECTED]> wrote: > As for the last problem, Although Sqlite's at fault, I think it would > be reasonable for Sequel to overcome Sqlite's shortcomings by allowing > access to the :"`name`" column via :name.
Ah, but no! Because, though crazy, it's legal to have columns with backticks on the name. The correct fixes would be, I think: A. Have Sequel always use an AS clause for all columns in selects. B. Have Sequel only use bacticks for reserved keywords or otherwise invalid column names. This would only fix the problem for the common case, though. C. Have Sequel remember the names of columns requested (which would require parsing SQL code in some cases). D. Have SQLite behave sensibly. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
