On 5 Oct 2010, at 9:40pm, Paweł Salawa wrote:
>> Maybe you should remove the "ON CONFLICT IGNORE" clause at the end of the
>> uniqueness constraint...
>
> You're right, of course.
> Shame on me for missing it :( Shame on me!
We all make mistakes like that. It's really useful to have someone el
> Maybe you should remove the "ON CONFLICT IGNORE" clause at the end of the
> uniqueness constraint...
You're right, of course.
Shame on me for missing it :( Shame on me!
--
Paweł Salawa
pawelsal...@gmail.com
___
sqlite-users mailing list
sqlite-users
On Tue, Oct 05, 2010 at 09:56:52PM +0200, Pawe?? Salawa scratched on the wall:
> Hi,
>
> My SQLite is 3.7.2.
>
> I have a table like this:
>
> CREATE TABLE [newsd] (
> [id] INTEGER PRIMARY KEY AUTOINCREMENT,
> [date] INTEGER NOT NULL, [title] TEXT NOT NULL,
> [yhfgdfhd] NONE,
> CONSTRAIN
On Tue, Oct 5, 2010 at 3:56 PM, Paweł Salawa wrote:
> Hi,
>
> My SQLite is 3.7.2.
>
> I have a table like this:
>
> CREATE TABLE [newsd] (
> [id] INTEGER PRIMARY KEY AUTOINCREMENT,
> [date] INTEGER NOT NULL, [title] TEXT NOT NULL,
> [yhfgdfhd] NONE,
> CONSTRAINT "fg" UNIQUE ([yhfgdfhd]) ON CO
Hi,
My SQLite is 3.7.2.
I have a table like this:
CREATE TABLE [newsd] (
[id] INTEGER PRIMARY KEY AUTOINCREMENT,
[date] INTEGER NOT NULL, [title] TEXT NOT NULL,
[yhfgdfhd] NONE,
CONSTRAINT "fg" UNIQUE ([yhfgdfhd]) ON CONFLICT IGNORE
)
so column [yhfgdfhd] is UNIQUE, and [title] is NOT N
5 matches
Mail list logo