y, MI
-Original Message-
From: Scott Hess [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 29, 2007 1:47 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] GUID/UUID in sqlite.
In either case, if you use the UUID as a primary key in more than one
table, you should consider having one table to co
In either case, if you use the UUID as a primary key in more than one
table, you should consider having one table to convert the UUID to a
64-bit id, and use that as the primary keys on the other tables. If
you have UUID as a primary key, your table will have 2 b-trees, one
for the index of UUID t
: sqlite-users@sqlite.org
Subject: Re: [sqlite] GUID/UUID in sqlite.
You could experiment with making your 128 bit entity a BLOB. The
alternative would be to represent it it in ASCII. Changing its radix
would probably be the significant overhead, not the Sqlite storage.
Prakash Reddy Bande wrote
You could experiment with making your 128 bit entity a BLOB. The
alternative would be to represent it it in ASCII. Changing its radix
would probably be the significant overhead, not the Sqlite storage.
Prakash Reddy Bande wrote:
Hi,
I am designing a database where-in my column data is UUID.
4 matches
Mail list logo