[sqlite] RDBMS handling of column names (was: Trouble with column names)
Hello Dr. Hipp, Hello dear sqlite users, following my post regarding how sqlite treats column names and the reply from Dr. Hipp, I've studied the way various RDBMS treat column names. The document containing the results obtained is attached to this message. The conclusions I can draw from these investigations is this: although not all queries tested work on all tested database engines, the ones that do work provide consistent results (e.g. SQL Server and MySQL yield the same results). Although things could further change in order to provide a uniform handling with column names, I only insist on one thing: if I ask for column Field1 and that column exists in the table as FIELD1, sqlite should return it as I ask, e.g. Field1 (instead of the way it does now, FIELD1). I cannot understand why this behavior has changed (it did not happen with 3.0.8). If this is not a bug, I guess it's a feature. If it's a feature, what advantages do I have if the database engine doesn't give me what I ask for? Please understand that I'm not trying to criticise anything or anyone: I'm just trying to understand why this has happened and why people do not complain about it. Thanks. George.
Re: [sqlite] RDBMS handling of column names (was: Trouble with column names)
Hello Dr. Hipp, Hello dear sqlite users, following my previous post: I did not know that I'm not allowed to post attachments in this group... I've added the document which compares how SQL Server, MySQL and sqlite treats column names as an attachment to the wiki page (http://www.sqlite.org/cvstrac/wiki?p=ColumnNames) created by Dr. Hipp. It can be found at: http://www.sqlite.org/cvstrac/attach_get/167/ColumnNames.htm George.
Re: [sqlite] RDBMS handling of column names (was: Trouble with column names)
George Ionescu said: ask for? Please understand that I'm not trying to criticise anything or anyone: I'm just trying to understand why this has happened and why people do not complain about it. George, I suspect very strongly that most SQLite users are submitting themselves to that discipline which I suggested in an earlier message, principally that we don't expect SQLite to cover for our own inconsistencies in column naming. The discipline is fairly simple and I heartily encourage you to submit to it. Clay Dowling -- Lazarus Notes from Lazarus Internet Development http://www.lazarusid.com/notes/ Articles, Reviews and Commentary on web development
Re: [sqlite] RDBMS handling of column names (was: Trouble with column names)
Hello Clay, thanks for replying to the message, I suspect very strongly that most SQLite users are submitting themselves to that discipline which I suggested in an earlier message, principally that we don't expect SQLite to cover for our own inconsistencies in column naming. The discipline is fairly simple and I heartily encourage you to submit to it. I do agree that programming requires discipline. I myself am quite disciplined in programming (well, that's my personal oppinion about me, some people may think differently). The trouble is that my users aren't :-) The SQLiteDb ActiveX wrapper is written by me. My users complain that after the 3.2.1 update they aren't able to reference columns unless they respect case-sensitivityness. And I, as an independent software developer, cannot send emails to clients asking them to be disciplined :-) I could change my code to perform a case-insensitive comparison for column names but that would lead to a performance penalty (big enough not to do it). On the other hand, if you've read the document attached on the wiki, you'll notice that there are differences in the way sqlite treats column names as opposed to SQL Server and MySQL. And I don't really think I'm asking much: all I want is that when I ask for Field1 column, the database engine to report Field1 and not FIELD1. Do you think this is a stupid think to ask? Thanks again. George.
Re: [sqlite] RDBMS handling of column names (was: Trouble with column names)
On Wed, 2005-04-27 at 15:53 +0300, George Ionescu wrote: And I don't really think I'm asking much: all I want is that when I ask for Field1 column, the database engine to report Field1 and not FIELD1. Set PRAGMA short_column_names=OFF; and that will happen. Why doesn't that solution work for you? -- D. Richard Hipp [EMAIL PROTECTED]
Re: [sqlite] RDBMS handling of column names (was: Trouble with column names)
Hello Dr. Hipp, Hello dear sqlite users, And I don't really think I'm asking much: all I want is that when I ask for Field1 column, the database engine to report Field1 and not FIELD1. Set PRAGMA short_column_names=OFF; and that will happen. Why doesn't that solution work for you? Hmmm, too much caffeine and less sleep! I didn't notice, neither by reading the docs nor by experimenting with command line tool, that setting short_column_names=OFF is just what I need and think is the correct way of handling column names. Sorry for insisting so much. I didn't want to start a riot... Thanks again. George.
RE: [sqlite] RDBMS handling of column names (was: Trouble with column names)
This is fine for me too. However, in 3.1.0 neither of these pragmas appeared to work. Are they fixed in a later release or check-in? Sorry, but I couldn't find this info on the website. -Original Message- From: George Ionescu [mailto:[EMAIL PROTECTED] Sent: 27 April 2005 14:18 To: sqlite-users@sqlite.org Subject: Re: [sqlite] RDBMS handling of column names (was: Trouble with column names) Hello Dr. Hipp, Hello dear sqlite users, And I don't really think I'm asking much: all I want is that when I ask for Field1 column, the database engine to report Field1 and not FIELD1. Set PRAGMA short_column_names=OFF; and that will happen. Why doesn't that solution work for you? Hmmm, too much caffeine and less sleep! I didn't notice, neither by reading the docs nor by experimenting with command line tool, that setting short_column_names=OFF is just what I need and think is the correct way of handling column names. Sorry for insisting so much. I didn't want to start a riot... Thanks again. George.
