Quoting Benoit Gregoire <[EMAIL PROTECTED]>:
>> > Fair enough, it's fixed length. But it will make for really ugly SQL for
>> > JOINS, with the only benefit of saving four bytes. I think using a
>> > varbinary is much preferable (and just as portable).
>>
>> Or a varchar(32) and the hexstring... Just as portable and actually
>> human-readable (and human-enterable). Not that I'm biased or anything
>> ;)
>
> I just didn't dare suggest it ;)
Eh, it's okay.. That's why I did. Another benefit of using the
hexstring instead of four integers -- it makes it easy for a human
to compare the DB contents to an XML file. And honestly, I can't
imagine the performance is going to be SO BAD that it'll be an issue.
-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
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
