If your table is defined as
CREATE TABLE table0 (col1 INTEGER, col2 TEXT, col3 INTEGER)
I believe the correct syntax would be:
SELECT col1, quote(col2) AS col2, col3 FROM table0;
Instead of * you list the columns, separated by comma. Since you're using
quote() around col2, you probably need
transaction a failure as well -- if for no
other reason than the technical limitations of my db wrapper. ;)
-Original Message-
From: Igor Tandetnik [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 03, 2005 1:21 PM
To: SQLite
Subject: [sqlite] Re: BEGIN TRANSACTION name
Marcus Welz wrote
I actually have a question regarding nested transactions. Maybe I'm missing
something, but isn't it true that the outermost transaction must be
committed successfully in order for any of the nested transactions to also
be committed successfully?
For example if I have:
BEGIN TRANSACTION a;
BEGIN
Indeed.
CREATE TABLE ex1(
x INTEGER,
y REAL,
CHECK(xmailto:[EMAIL PROTECTED]
Sent: Wednesday, November 02, 2005 8:12 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] CHECK constraints
*snip*
At least in Oracle, no, your example insert works fine. If you want
the insert to
e: [sqlite] CHECK constraints
"Marcus Welz" <[EMAIL PROTECTED]> wrote:
> PostgreSQL 8.0 will happily insert (5, NULL).
>
Hmmm.. Not what I expected, nor what I implemented.
But the implementation is easily changed and there is
no point in trying to be "logical" abo
PostgreSQL 8.0 will happily insert (5, NULL).
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 02, 2005 6:31 PM
To: sqlite-users@sqlite.org
Subject: [sqlite] CHECK constraints
In a CHECK constraint, if the expression is NULL (neither true
or [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 08, 2005 6:50 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] SUM and NULL values
On Sep 8, 2005, at 5:45 PM, Marcus Welz wrote:
> If "SELECT SUM(amt)" means "How much did I sell?"
>
> Then the "
If "SELECT SUM(amt)" means "How much did I sell?"
Then the "NULL" should mean, "You didn't sell anything.", no?
To me, there is a difference between 0 ("You sold merchandise worth $0"
perhaps because of sweepstakes, giveaway, rebate coupons, etc) and NULL
("You didn't sell anything.").
I think
For some reason I have to agree with the SQL standard, which I would
interprete as the following (and this may not be all that bullet proof):
"If the result set contains numeric values, sum them up, ignoring NULLs. If
there are no numeric values present (the result set is either empty or
contains
Hello there,
I think that adhering to standards is a Very Good Thing(tm). They are
standards for a reason. Deviations can introduce ambiguity, confusion,
complexity, vendor lock-ins and all sorts of other headaches.
That said, however, I believe that "no, because it's not the standard" isn't
10 matches
Mail list logo
