Imho, naming scheme should be like this:
1. column names as returned from sqlite3_column_name should always be a
single word,
NOT qualified by origin.
So, all below should return "field1" as column name.
If there is a column alias in the select, the *alias* should be returned
as the single word.
C
On Wed, 2005-04-27 at 13:19 +, Tiago Dionizio wrote:
> On 4/27/05, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
> > I have closed all these tickets now. See wiki page
> > http://www.sqlite.org/cvstrac/wiki?p=ColumnNames
>
> Isn't the pragma long_column_names supposed to be full_column_names?
>
On 4/27/05, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
> I have closed all these tickets now. See wiki page
> http://www.sqlite.org/cvstrac/wiki?p=ColumnNames
Isn't the pragma long_column_names supposed to be full_column_names?
Using long_column_names doesn't seem to work on the command line.
(Al
On Mon, 2005-04-25 at 15:12 +0300, George Ionescu wrote:
> while working with sqlite v3.2.1, I've noticed another annoyance in
> the way sqlite returns column names (besides the bug with #1141,
> duplicated as #1218).
>
I have closed all these tickets now. See wiki page
http://www.sqlite.org/cvst
D. Richard Hipp wrote:
Please tell me what *you* think the column name should be in
the following cases. Also, please tell me what PostgreSQL and
MySQL and perhaps Oracle do. The decision of how to name
result columns is complex and I am unwilling to go about
making random changes here and there
George Ionescu said:
> notice the uppercase F from Field1, although field1 is requested.
> So, it seems that sqlite returns column names as defined in schema, not as
> requested by the user. This may not seem a big problem, but it becomes one
> when working with columns and trying to refer them b
-Original Message-
From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
Sent: Monday, April 25, 2005 8:37 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Trouble with column names
On Mon, 2005-04-25 at 15:12 +0300, George Ionescu wrote:
> sqlite3 test.db
> create table test(Field1 t
p [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 25, 2005 9:37 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Trouble with column names
>
> On Mon, 2005-04-25 at 15:12 +0300, George Ionescu wrote:
> > sqlite3 test.db
> > create table test(Field1 text(20));
> >
On Mon, 2005-04-25 at 15:12 +0300, George Ionescu wrote:
> sqlite3 test.db
> create table test(Field1 text(20));
> insert into test values ('a value');
> select field1 from test;
>
Please tell me what *you* think the column name should be in
the following cases. Also, please tell me what Postgre
>>notice the uppercase F from Field1, although field1 is requested.
>>So, it seems that sqlite returns column names as defined in schema, not as
>>requested by the user. This may not seem a big problem, but it becomes one
>>when working with columns and trying to refer them by name and not wantin
Op maandag 25 april 2005 14:12, schreef George Ionescu:
> Hello Dr. Hipp,
> Hello dear sqlite users,
>
> while working with sqlite v3.2.1, I've noticed another annoyance in the way
> sqlite returns column names (besides the bug with #1141, duplicated as
> #1218).
>
> Using sqlite command line, ente
>notice the uppercase F from Field1, although field1 is requested.
>So, it seems that sqlite returns column names as defined in schema, not as
>requested by the user. This may not seem a big problem, but it becomes one
>when working with columns and trying to refer them by name and not wanting t
12 matches
Mail list logo
