|Subject||RE: [IB-Architect] assert triggers and server aborts|
|Author||Claudio Valderrama C.|
> -----Original Message-----BLOBs accept charsets but not collations. Also, when you order by a BLOB
> From: Mike Nordell [mailto:tamlin@...]
> Sent: Domingo 13 de Agosto de 2000 1:31
> Suggestion from a dev-list pointed me here with this problem, since
> IB-Architect would be the more probable list to find someone that
> knows, if
> even partially, this code.
> Preconditions: debug build with DEV_BUILD macro defined.
> SELECT DISTINCT RDB$DESCRIPTION FROM RDB$RELATIONS;
> This results in an triggered assert
> assert (sort_key->skd_dtype != 0);
> at (or about) line 4287 in jrd/opt.c.
field, the documentation states this cannot be done and in practice, the
ordering is using the BLOB_ID.
So, the release build simply allows such code to run, but the result is
unmeaningful for the user, unless he/she's really trying to discover the
order of the BLOB_IDs.
I think that it should be left as it's. In the debug release, probably an
assertion is the way to proceed.