Subject | RE: [ib-support] OID: Double or String? |
---|---|
Author | PODESTA Mariano APRE |
Post date | 2002-08-29T19:00:45Z |
a guid is a 128 bit number, not a string.
> -----Original Message-----
> From: PUB: Guillermo Najar-Arreola [mailto:gnajar@...]
> Sent: Jueves, 29 de Agosto de 2002 14:25
> To: ib-support@yahoogroups.com
> Subject: Re: [ib-support] OID: Double or String?
>
>
> Hi,
>
> I found that GUID is a beautifull candidate for OID; the
> point is that its a
> string. How much I loose in performance if I use a string primary-key
> instead of a numeric one ?
>
> Thank you,
> Guillermo
>
> ""Leyne, Sean"" <sleyne@...> wrote in message
> news:66187D861C1747499BE1365B74E0369110ACCC@......
> >
> > OIDs???
> >
> > > -----Original Message-----
> > > From: Guillermo Najar-Arreola [mailto:gnajar@...]
> > > Sent: Wednesday, August 28, 2002 4:22 PM
> > > To: ib-support@yahoogroups.com
> > > Subject: [ib-support] OID: Double or String?
> > >
> > >
> > > Hi,
> > > I'm planning how am I going to implement OIDs for any of
> my apps using
> > > Firebird. I was thinking on strings since I have customers
> > > with laptops that
> > > download their information to a central server and I want to
> > > prefix the OID
> > > comming from each computer so I don't have conflicts with
> > > OIDs generated in
> > > the central server. For Interbase, what data type is more
> > > efficient for primary keys ? double or string?
> >
> >
> > To unsubscribe from this group, send an email to:
> > ib-support-unsubscribe@egroups.com
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
> >
> >
> >
>
>
>
> ------------------------ Yahoo! Groups Sponsor
> ---------------------~-->
> 4 DVDs Free +s&p Join Now
> http://us.click.yahoo.com/pt6YBB/NXiEAA/MVfIAA/67folB/TM
> --------------------------------------------------------------
> -------~->
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>