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

Bug #4351 notnull -> false needs a default value
Submitted: 2005-05-15 17:01 UTC
From: dufuz Assigned: lsmith
Status: Closed Package: MDB2_Schema
PHP Version: 4.3.11 OS: Fedora Core 3
Roadmaps: (Not assigned)    

 [2005-05-15 17:01 UTC] dufuz
Description: ------------ Here's the field in question: <field> <name>term</name> <type>text</type> <length>240</length> <notnull>false</notnull> </field> and the error message that I get is: Parser error: if field is "notnull", it needs a default value - Byte: 588; Line: 30; Col: 3 Kind illogical since I'm saying false, hence it should be NULL :-) I realize that I should be using <null>true</null> rather if that exists, but well think about it if someone is auto generating, easier to change the option than the tags around the option :P


 [2005-05-16 00:51 UTC] dufuz
The fix you gave me "fixes" the problem, I do not get the error anymore, but still the field is created as not null even tho I pass the false. So anyway, in theory this bug is fixed, do you want to track the other thing I mentioned in this bug report or shall I open a new one ?
 [2005-05-16 13:44 UTC] smith at backendmedia dot com
Yes please open a new one on MDB2 (not MDB2_Schema)
 [2005-05-18 05:44 UTC] dufuz
Opened up the new bug report as requested, changing the summary here, only thing needed is a commit from you when you arrive back.
 [2005-05-19 14:36 UTC] smith at backendmedia dot com
This bug has been fixed in CVS. In case this was a documentation problem, the fix will show up at the end of next Sunday (CET) on In case this was a website problem, the change will show up on the website in short time. Thank you for the report, and for helping us make PEAR better.