Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.5.0b5

Bug #6494 table not found in tableInfo() when having lower case table names
Submitted: 2006-01-15 11:21 UTC
From: wiesemann Assigned: quipo
Status: Closed Package: MDB2_Driver_ibase
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 22 + 24 = ?

 
 [2006-01-15 11:21 UTC] wiesemann
Description: ------------ When I use createTable() with a lower case table name ('test2' in my case) and call then tableInfo() with this lower case table name, the result is: Warning: ibase_query(): Dynamic SQL Error SQL error code = -204 Table unknown TEST2 At line 1, column 21. in E:\htdocs\pear\PEAR\MDB2\Driver\ibase.php on line 491 string(165) [Last query: SELECT * FROM test2 WHERE 1=0] [Native code: -204] [Native message: Dynamic SQL Error SQL error code = -204 Table unknown TEST2 At line 1, column 21. ] Altough one can see 'TEST2' twice in upper case letters in the quotation, the query uses 'test2'.

Comments

 [2006-01-15 15:25 UTC] wiesemann
Strange: Setting $result to upper case before doing the query results in the same error, although the table definitely exists and the query 'SELECT * FROM TEST2 WHERE 1=0' works as expected when executed in a tool like IBExpert (works also with lower case name). Auto commit is active (default), so this should actually not be the problem.
 [2006-01-16 11:11 UTC] quipo
are you creating the table and then checking it in *the same* script? If so, I experience the same issue, but I don't have the slightest idea on why it happens. Try doing an explicit $db->exec('COMMIT') query before the call to tableInfo(). Does PEAR::DB have the same behaviour?
 [2006-01-16 11:36 UTC] wiesemann
> are you creating the table and then checking it in *the > same* script? If so, I experience the same issue, but I > don't have the slightest idea on why it happens. Yes, same script. > Try doing an explicit $db->exec('COMMIT') query before > the call to tableInfo(). That works. The table is found. > Does PEAR::DB have the same behaviour? No, with DB it works (without the explicit COMMIT). Very strange.
 [2006-01-20 12:12 UTC] quipo
should be fixed. Can you check the latest CVS version, I've committed a workaround for this issue.
 [2006-01-22 16:07 UTC] wiesemann
Thanks, the new CVS version works as expected.