Page 2 of 2
Re: 0 record(s) updated. Only one record should have been up
Posted: 25.11.2013, 15:15
by tuxracer78
The problem seems to be solved.
After applying the patch, posting the queries now works without error messages. The % has disappeared from the "find primary key statement", as I can see via SQLMonitor.
Thanks
Gregor
Re: 0 record(s) updated. Only one record should have been up
Posted: 25.11.2013, 21:12
by mdaems
SVN rev. 2948 (7.2-testing).
Can be merged to 7.1 soon.
I'm aware this patch is insufficient for IB/FB, but I need a user specialized in this databases to find out how this can be solved.
Mark
Re: 0 record(s) updated. Only one record should have been up
Posted: 27.11.2013, 09:55
by marsupilami
Hello Mark,
I did some experiments on that and it seems that this has to do with the way, the like predicate works (in Firebid?) and the Firebird design decision to expose character data in the system tables using the CHAR(n) datatype. For doing a like comparison it seems, one has to get rid of the trailing spaces of the CHAR(n) data type. Given a table of the name TABLE_NAME, this will not work:
SELECT * FROM RDB$RELATIONS where RDB$RELATION_NAME like 'TABLE%NAME'
whereas
SELECT * FROM RDB$RELATIONS where trim(RDB$RELATION_NAME) like 'TABLE%NAME'
will work as expected. I tested this on Firebird 2.5.
Best regards,
Jan
Re: 0 record(s) updated. Only one record should have been up
Posted: 03.12.2013, 16:34
by EgonHugeist
Thank you, Jan. Mark did apply your proposal. Great job again!