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

Bug #16281 getTableFieldDefinition() does not recognize NULL defaults with datatype
Submitted: 2009-06-03 18:40 UTC
From: hschletz Assigned: quipo
Status: Closed Package: MDB2_Driver_pgsql (version 1.5.0b2)
PHP Version: Irrelevant OS:
Roadmaps: (Not assigned)    

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:
Solve the problem : 38 + 46 = ?

 [2009-06-03 18:40 UTC] hschletz (Holger Schletz)
Description: ------------ After Upgrading PostgreSQL from 8.1 to 8.3 and heavily mangling some tables through MDB2_Schema, some (not all) columns now have a default like "NULL::character varying (255)" instead of plain "NULL". This is a bit odd, but not really a problem. Unfortunately, getTableFieldDefinition() does not recognize this as NULL and returns the complete string literally. Fix attached.


 [2009-06-03 18:41 UTC] hschletz (Holger Schletz)
The following patch has been added/updated: Patch Name: recognize-null-default-with-datatype Revision: 1244036504 URL:
 [2009-06-21 15:21 UTC] quipo (Lorenzo Alberton)
-Status: Open +Status: Closed -Assigned To: +Assigned To: quipo
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.