> We just use GUIDs here for IDs (as our software runs in a 3-tier
> environment
> its better, because we can generate the ID on the client side), and aside
> from the little problems mentioned by Alan (which aren't real problems) we
> don't have any complaints.

you're aware that GUIDs provide poor indexing with FB's index trees don't
you?
Are you happy with your PK index selectivity?
Alan

>
> On 10/18/07, Lee Jenkins <lee@...> wrote:
> >
> > Alan McDonald wrote:
> > >
> > >
> > > > I think I read somewhere that long strings such as GUIDs for PK's in
> > > > Firebird were problematic. Is there any truth to this?
> > > >
> > > > Thanks,
> > > >
> > > > --
> > > > Warm Regards,
> > > >
> > > > Lee
> > >
> > > not probmelatic but to some degree, annoyance.
> > > there's a UDF which generates UUID - better than GUID for FB indexing,
> > so
> > > use it and not GUID generation.
> > > other annoyances,
> > > more disk space (it's cheap)
> > > impossible to humanly determine record creation sequence without
> > additonaly
> > > timestamp (more disk splace - it's cheap)
> > > there are other ways to guarantee unique keys but using
> BIGINT instead.
> > > more load on transport protocol when transferring data OTW
> > > there may be others
> > > Alan
> >
> > Thanks for the input, Alan.
> >
> > --
> > Warm Regards,
> >
> > Lee