2006/10/30, Derek Atkins <[EMAIL PROTECTED]>:
> Phil Longstaff <[EMAIL PROTECTED]> writes:
>
> >> Sorry, what I meant was that I didn't understand what you meant by
> >> "small add-on".. I don't know GDA well-enough to know what that means
> >> or how that would work.
> >>
> >> > Phil
> >
> > I ha
Phil Longstaff <[EMAIL PROTECTED]> writes:
>> Sorry, what I meant was that I didn't understand what you meant by
>> "small add-on".. I don't know GDA well-enough to know what that means
>> or how that would work.
>>
>> > Phil
>
> I haven't thought this through entirely, but these are my first
>
On Sat, 2006-28-10 at 11:46 -0400, Derek Atkins wrote:
> Phil Longstaff <[EMAIL PROTECTED]> writes:
>
> >> > 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 fo
Phil Longstaff <[EMAIL PROTECTED]> writes:
>> > 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 d
On Fri, 2006-27-10 at 12:33 -0400, Derek Atkins wrote:
> Quoting Phil Longstaff <[EMAIL PROTECTED]>:
>
> >> 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 bein
Quoting Phil Longstaff <[EMAIL PROTECTED]>:
>> 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
On Fri, 2006-27-10 at 12:01 -0400, Derek Atkins wrote:
> Phil Longstaff <[EMAIL PROTECTED]> writes:
>
> >> I suppose we could use varchar; the guid has a fixed size so we know
> >> exactly how much space it requires. It's just an MD5 hash, so it's
> >> 128 bits, which is 16 bytes of binary or 32
Phil Longstaff <[EMAIL PROTECTED]> writes:
>> I suppose we could use varchar; the guid has a fixed size so we know
>> exactly how much space it requires. It's just an MD5 hash, so it's
>> 128 bits, which is 16 bytes of binary or 32 bytes of Hexstring.
>
> I am looking at having an int as the prim
On Thursday 26 October 2006 14:49, Phil Longstaff wrote:
> On Thu, 2006-26-10 at 09:53 -0400, Derek Atkins wrote:
> > Mark Johnson <[EMAIL PROTECTED]> writes:
> > > I may be getting a bit ahead of the play here, since you are talking
> > > about design still, and I am thinking about implementation
Quoting Phil Longstaff <[EMAIL PROTECTED]>:
> I am looking at having an int as the primary key for references to a
> table. The GUID would be stored with the row as 4 ints (guid_1, guid_2,
> guid_3 and guid_4). If we need to search a lot by GUID, we could have
> an index which spans those 4 colu
10 matches
Mail list logo
