On Sep 11, 2008, at 10:49 AM, Igor Tandetnik wrote: > Gavin Kistner <[EMAIL PROTECTED]> wrote: >> The presence of backticks in the column header name is causing the >> ORB >> library I'm working with to think that the name of the column is >> "`bar`" instead of "bar". >> See: >> http://groups.google.com/group/sequel-talk/browse_frm/thread/915c6f807f6d61c1 >> >> May this properly be considered a bug in SQLite? > > http://www.mail-archive.com/sqlite-users@sqlite.org/msg36030.html
Thank you for the swift followup. I did search before posting, but was searching for "backtick" instead of "grave accent". Upon reading that thread, however, I'm not exactly sure how it applied. The thread mentions backticks as topic #2, but proposes removing the use of double-quoted (topic #3). All followup replies seem to be in favor of removing double-quotes, with no further mention of backticks/grave accents. Perhaps your intention in posting that link was to note that there are other ways to quote column names. As backticks are included for MySQL compatibility, and the library I'm utilizing is using[1] backticks (for presumably the same reason) I'm not at liberty to change how the quotation happens. So I ask again: can the inclusion of backticks in the column name returned as the result for certain select statements be considered a bug? [1] http://sequel.rubyforge.org/ _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
