While these ideas are great workarounds they have many
hurdles. What I'm looking for is a clean
implementation that isn't a hack. The only way this
can be achieved is for Firebird to actually support
this data type directly.

The problem with CHAR(16) fields (been there done
that!) is that you run into problems with special
characters- e.g. ASCII 0 terminates the string etc.
While the database may handle this properly there are
invariably some bugs in database libraries that
truncate the field "by accident" (i.e. bug) so it
really isn't a workable solution.

With two bigints you have the pain of dealing with two
fields instead of just one. Retrieving and
manipulating the value is problematic. Composite
primary keys can also be a pain- it is nicer to have a
single GUID key field to manipulate. Your SQL is a
lot simpler etc.

How do I add a feature request for Firebird?? I've
seen a place to report a bug but nowhere to add
feature requests. I'd like to add this as a feature
request.

Thanks,
Kevin.

--- Lester Caine <lester@...> wrote:

>
> >> I think there's no 128-bit integer
> >>in firebird, is there?).
> >
> > Correct it doesn't exist.
>
> Just use a pair of BIGINT's ?
>
> --
> Lester Caine
> -----------------------------
> L.S.Caine Electronic Services
>
>
>
> Yahoo! Groups Links
>
> http://groups.yahoo.com/group/Firebird-Architect/
>
> Firebird-Architect-unsubscribe@yahoogroups.com
>
>
>
>
>
>

__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/