-Original Message-
From: Darren Duncan [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 20, 2004 3:14 PM
To: [EMAIL PROTECTED]
Subject: RE: [sqlite] sqlite project--working with table structure
-- Darren Duncan
ok Darren. Thank you and the other posters for helping.
I will think
At 5:40 AM -0500 11/20/04, j-marvin wrote:
Darren, this is cool. I can't wait to pass this along to a person
at my job who works with DB's at his full-time job.
Thanks, I appreciate it. Note also that another release of
SQL::Routine should be posted on CPAN either today or tomorrow.
I had
Ulrik Petersen wrote:
> [T]he way I understand SQLite, if you delete a row with the DELETE
> statement, the row will not actually be deleted, only marked as
> deleted. Then the next time you insert a row, the row may be reused.
> At least that's how I understand it... could somebody please
Hi Jim,
> hi-
>
> i was hoping to get a little feedback on an idea i had.
>
> the create table statement can get complex with its variable number
> field constraints and table constraints etc. etc.
> when i first tackled the problem i tried to parse it. now i have a
> different idea. what if i
Have a look here: http://search.cpan.org/dist/SQL-Routine/
That's part of a project I'm working on. With it, each database
table, as well as every other kind of thing you could possibly put in
a schema or use with a database, is represented as a cross-referenced
hierarchy of atomic-value
At 3:37 AM -0500 11/20/04, j-marvin wrote:
hi-
i was hoping to get a little feedback on an idea i had.
the create table statement can get complex with its variable number
field constraints and table constraints etc. etc.
when i first tackled the problem i tried to parse it. now i have a
different
6 matches
Mail list logo
