Hello Dennis Cote,
>This should probably be fixed when your proposal is implemented.
I just pray and hope that it will ...
Ralf
Hi Derrel
> --- Ursprüngliche Nachricht ---
> Von: [EMAIL PROTECTED]
> An: sqlite-users@sqlite.org
> Betreff: Re: [sqlite] Proposal: sqlite3_column_rowid
> Datum: Tue, 16 May 2006 09:12:37 -0400
> What does it do with queries that are pulling data from multiple tables?
>
Ralf Junker wrote:
Even if sqlite3_column_rowid can sometimes not exactly identify a data
field, it can still do so reliably with the majority of queries IMHO.
It could at least do so much better than any other work-around I can
think of. This would finally enable applications to allow users to
Hello Dennis,
please ignore my previous response - it is all wrong because I used the wrong
table definitions and data (see below for corrections). My appologies for this,
and thanks for holding on to sqlite3_column_rowid.
>I like your proposal, and I understand what you want it for (at least I
On 5/16/06, Dennis Cote <[EMAIL PROTECTED]> wrote:
> SELECT c1, c2, c3 FROM a JOIN b USING(c1);
>
> Preparing this returns SQLITE_ERROR with message "ambiguous column name:
c2".
>
This is wrong. Column c2 only exists in table b and so it can't be
ambiguous. I suspect you are using different
Ralf Junker wrote:
SELECT c1, c2, c3 FROM a NATURAL JOIN b;
SELECT c1, c2, c3 FROM a JOIN b USING(c1);
There is no way to know which table the c1 column value is associated with
(technically the selected columns in such joins don't belong to either table
according to the SQL standard) so no
Hello Dennis Cote,
> SELECT c1, c2, c3 FROM a NATURAL JOIN b;
> SELECT c1, c2, c3 FROM a JOIN b USING(c1);
>
>There is no way to know which table the c1 column value is associated with
>(technically the selected columns in such joins don't belong to either table
>according to the SQL standard) s
>What does it do with queries that are pulling data from multiple tables? How
>about computed column data?
>
>Consider these queries:
>
> SELECT a.c2, b.c3 FROM a, b WHERE a.c1 = b.c1;
For field a.c2:
* sqlite3_column_rowid(0) returns RowID for field 'a2' in table 'a' from
which the va
[EMAIL PROTECTED] wrote:
What does it do with queries that are pulling data from multiple tables? How
about computed column data?
Consider these queries:
SELECT a.c2, b.c3 FROM a, b WHERE a.c1 = b.c1;
SELECT c1 + c2 FROM a;
Derrell,
I don't see a problem with either of your problem que
Ralf Junker <[EMAIL PROTECTED]> writes:
> Drawbacks on sqlite3_column_rowid?
>
> I can not see any negatives on sqlite3_column_rowid.
What does it do with queries that are pulling data from multiple tables? How
about computed column data?
Consider these queries:
SELECT a.c2, b.c3 FROM a, b
Hello to all,
I would like to propose a new API function:
long long int sqlite3_column_rowid(sqlite3_stmt*, int iCol);
As the name implies, this function would return the RowID for a given column
after sqlite3_step has returned SQLITE_DATA. The RowID would be valid for the
database and table
11 matches
Mail list logo
