Marcello, Lester, All,

Firebird-general@yahoogroups.com, Lester Caine <lester@l...> wrote:
[...]

> The TikiWiki database has a lot of long keys because they use long
> VARCHAR fields for Primary Keys.

[...]

> > Does anybody know if FB 1.5 solves this issue?
>
> Simply copying bad design may not actually be solving a problem just
> perpetuating it ;)

On a recent similiar discussion I proposed to cope
with long strings which must be indexed, by using a
loadable collation which replaces the tail of the string
with a hash key:

"A long string which is unwisely be choosen as primary key"
=>
"A long str {4DF543E5}"

This will actually work, and would be invisible to the
app (if sorting only on the first N chars is good enough),
but of course it's a hack.

Regards,
Peter Jacobi