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
0 record(s) updated. Only one record should have been update
-
- Fresh Boarder
- Posts: 7
- Joined: 24.01.2008, 11:53
- mdaems
- Zeos Project Manager
- Posts: 2766
- Joined: 20.09.2005, 15:28
- Location: Brussels, Belgium
- Contact:
Re: 0 record(s) updated. Only one record should have been up
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
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
-
- Platinum Boarder
- Posts: 1956
- Joined: 17.01.2011, 14:17
Re: 0 record(s) updated. Only one record should have been up
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
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
- EgonHugeist
- Zeos Project Manager
- Posts: 1936
- Joined: 31.03.2011, 22:38
Re: 0 record(s) updated. Only one record should have been up
Thank you, Jan. Mark did apply your proposal. Great job again!
Best regards, Michael
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/
You want to help? http://zeoslib.sourceforge.net/viewtopic.php?f=4&t=3671
You found a (possible) bug? Use the new bugtracker dude! http://sourceforge.net/p/zeoslib/tickets/