[Firebird-devel] [FB-Tracker] Created: (CORE-2712) Do not print "invalid request BLR" for par.cpp errors with valid BLR

[Bill O. (JIRA) <tr...@fi...>]

Do not print "invalid request BLR" for par.cpp errors with valid BLR
--------------------------------------------------------------------

                 Key: CORE-2712
                 URL: http://tracker.firebirdsql.org/browse/CORE-2712
             Project: Firebird Core
          Issue Type: Improvement
          Components: Engine
    Affects Versions: 2.5 Beta 2
         Environment: reported on windows XP, portable
            Reporter: Bill Oliver
            Priority: Minor


I have a test case which attempts to update a column value in a shared table with a where clause using multiple threads. The error returned is  "invalid request BLR at offset 24 - table id 428 is not defined". The expected SQLSTATE of 42S02 is returned.

The error message is true - yes, we cannot find the table as it has already been dropped. This part is ok.

The "invalid request BLR" portion of the error message leads the user to believe that there is a Firebird bug - why is my BLR invalid? It is kind of scary. In this case, the BLR is valid - it's just that we can't find the table - it has already been deleted.

An improvement would just be for the error message to simply say, "Table id 428 was not found", or "Table id 428 no longer exists". I think the 2nd form is ok, since if we have an ID the table must have existed at some point, right?

SQLSTATE of 42S02 is correct and should be preserved for this case if new message is added.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira