Subject | Re: Problems with table RDB$PROCEDURES |
---|---|
Author | Ann W. Harrison |
Post date | 2004-01-24T18:05:12Z |
At 12:28 PM 1/24/2004, Marc Geldon (PRO IT SYSTEMS) wrote:
though gbak and a few of the other utilities do it. BLR
(Binary Language Representation) is a binary coded relational
statement, or in other words, gook. By convention, a BLR
string starts with the version number which should be 4
or 5. The "expected 4, encountered 98" part of the message
says that the string you stored started with a 98 ('b') (hex
62).
bug. May I ask why you want to update that field?
Regards,
Ann
>Updating BLR fields directly is not a usual thing to do,
>If I try to update a row in RDB$PROCEDURES (I talk about the specific
>column RDB$PROCEDURE_BLR) and try to insert data, everytime I get the
>following message:
>....
>invalid request BLR at offset 0
>corrupt system table
>unsupported BLR version (expected 4, encountered 98)
though gbak and a few of the other utilities do it. BLR
(Binary Language Representation) is a binary coded relational
statement, or in other words, gook. By convention, a BLR
string starts with the version number which should be 4
or 5. The "expected 4, encountered 98" part of the message
says that the string you stored started with a 98 ('b') (hex
62).
>I get the same message if I update the row and set the same data thatAre you sure it's exactly the same?
>already was in the column.
>I don't know exactly what's going on but I doubt that it's a
>What is wrong here? Is that a bug?
bug. May I ask why you want to update that field?
Regards,
Ann