I understand your solution Woody, but it isn't practical for me, not for my
home shopping list program. A full on relational database like that is an
awful lot of work and it's only for home use (and any other family I can con
into using it and testing it).
I'd go for the relational route if I
, it just depends upon how you want to
partition your code.
Woody
from his pda
-Original Message-
From: flakpit [EMAIL PROTECTED]
Sent: Tuesday, July 01, 2008 11:00 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Multiple constraints per table?
I understand your solution Woody
Harold Wood amp; Meyuni Gani wrote:
U, hmm. The tips I gave you were from my pda based shopping program
that will be selling for 9.99 soon.
Good on you Woody, hope you sell a lot.! If my eyes were up to the challenge
of reading my PDA's small screen, i'd buy a copy and save myself
Lol. Thanks. If you want a schema I can attach and send to you.
Woody
from his pda
-Original Message-
From: flakpit [EMAIL PROTECTED]
Sent: Tuesday, July 01, 2008 11:30 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Multiple constraints per table?
Harold Wood amp; Meyuni Gani
flakpit [EMAIL PROTECTED]
wrote in message news:[EMAIL PROTECTED]
is it legal sql syntax to allow more than one constraint field in
table creation? I need at least these four below to guarantee that
duplicate items do make it into the database but not on the same day.
item TEXT CONSTRAINT
table, an item table, a
purchase history table as well as store_carried table.
just imho.
Woody
--- On Tue, 7/1/08, flakpit [EMAIL PROTECTED] wrote:
From: flakpit [EMAIL PROTECTED]
Subject: [sqlite] Multiple constraints per table?
To: sqlite-users@sqlite.org
Date: Tuesday, July 1, 2008, 1:10
Thank you Igor, the solution below (that you also posted) is what I found in
the forums after hours of searching when I should have been asleep. And
rather that produce shoddy code, I downloaded a proper sqlite tool to verify
that it was all working fine. Thank you for the response, I have
This is the way I normally create my shopping database, but this leads to
thousands of duplicates.
CREATE TABLE shopping(item TEXT,units TEXT,quantity TEXT,category TEXT,shop
TEXT,aisle TEXT,price TEXT,total TEXT,date TEXT,note TEXT,record INTEGER
PRIMARY KEY AUTOINCREMENT)
'item' is the full
