On Sat, 28 Feb 2004 11:52:03 +0100, Jakub Adamek <[EMAIL PROTECTED]> wrote:
> Is it really so that some database server returns a result set with two
> same column names? Seems very strange. And the lovely SQLite 3.0.8
> didn't do such things ...
PostgreSQL, which holds closer to the SQL spec
> The last one is really annoying and I can't believe the
> auto-tests could have missed it ...
>
>create table a (id, x);
>create table b (id, y);
>insert into a values (1,1);
>insert into b values (1,2);
>select * from a inner join b;
>
> column names returned:
Jakub Adamek wrote:
select * from a inner join b;
Just as a general guide with any database system, this type of query
isn't particularly recommended because of the namespace issue. Here's
what I do to get around the problem (again, not just with SQLite):
1. Specify the criteria for the join
: [sqlite] Version 3.1.3 is a headache
On Sat, 2005-02-26 at 22:43 +0100, Jakub Adamek wrote:
> Hi, I really love SQLite, but upgrading to 3.1.3 was not a good idea.
> I have already posted 3 tickets with rather serious problems with
> column names.
>
> The last one is really
On Sat, 2005-02-26 at 22:43 +0100, Jakub Adamek wrote:
> Hi, I really love SQLite, but upgrading to 3.1.3 was not a good idea. I
> have already posted 3 tickets with rather serious problems with column
> names.
>
> The last one is really annoying and I can't believe the auto-tests could
> have
2005 10:43 PM
Subject: [sqlite] Version 3.1.3 is a headache
> Hi, I really love SQLite, but upgrading to 3.1.3 was not a good idea. I
> have already posted 3 tickets with rather serious problems with column
> names.
>
> The last one is really annoying and I can't believ
Hi, I really love SQLite, but upgrading to 3.1.3 was not a good idea. I
have already posted 3 tickets with rather serious problems with column
names.
The last one is really annoying and I can't believe the auto-tests could
have missed it ...
create table a (id, x);
create table b (id, y);
7 matches
Mail list logo
