On 7/02/2020 20:08, Aapo Rantalainen wrote:
Hi, I'm just doing some 'software archeology' and I found that:
on Nov 21 01:02:00 2004
FossilOrigin-Name: ac72a1d5518f7b505ae2a1bd3be3d71db461ae7e
git: f8565825622a1ed48bdaa835968a1137b2ffa593
This sentence have been dropped out of documentation:
Hi, I'm just doing some 'software archeology' and I found that:
on Nov 21 01:02:00 2004
FossilOrigin-Name: ac72a1d5518f7b505ae2a1bd3be3d71db461ae7e
git: f8565825622a1ed48bdaa835968a1137b2ffa593
This sentence have been dropped out of documentation:
"Keyword matching in SQLite is case-insensitive."
Dixon Hutchinson <[EMAIL PROTECTED]> wrote:
> I have an SQLite db with one TEXT column. That column and an INTEGER
> column (not the rowid as this column is definitely not unique by itself)
> are declared UNIQUE together.
>
> CREATE TABLE foo (
> bar TEXT,
> p INTEGER,
> rowid
Dixon Hutchinson wrote:
I have an SQLite db with one TEXT column. That column and an INTEGER
column (not the rowid as this column is definitely not unique by
itself) are declared UNIQUE together.
CREATE TABLE foo (
bar TEXT,
p INTEGER,
rowid INTEGER PRIMARY KEY AUTOINCREMENT, -- I
I have an SQLite db with one TEXT column. That column and an INTEGER
column (not the rowid as this column is definitely not unique by itself)
are declared UNIQUE together.
CREATE TABLE foo (
bar TEXT,
p INTEGER,
rowid INTEGER PRIMARY KEY AUTOINCREMENT, -- I know... this is
5 matches
Mail list logo