GUIDs (was Re: SQL backend for GnuCash 2)

[Derek Atkins]

Quoting Phil Longstaff <plongstaff at rogers.com>:

>> I still don't understand why you want to do this.  What does it buy
>> us?  It seems to add a LOT of complexity on the GnuCash side when
>> building up SQL queries.  Instead of just being able to print out
>> "$table.${object}_id='$guid'" we'd need a much more complicated SQL
>> generator routine.
>
> I'm changing this to char(16).   I'm still concerned about 0x00 in a
> GUID.  The SQLite documentation says that memcmp is used to compare char
> strings, so that is OK, but I don't know about other db's.  MySQL
> supports binary(16), but other db's may not.

Make it "char(32)" and use the ascii hex-string representation.

> Since the connection string will be db-specific, we may want a db core
> built around libgda (see libgda vs libdbi e-mail) with a small add-on to
> handle the connection string formatting and how guid's will be handled
> (as well as adding db-specific indexes, stored procedures, ...).

Hmm.. I dont know how that might work..  But maybe that's because I
don't know GDA well enough.

> Phil

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available