RE: [PEAR] Problem with PEAR::MDB
| From: | Lukas Smith | Date: | Fri, 20 Jun 2003 11:32:54 +0000 |
| Subject: | RE: [PEAR] Problem with PEAR::MDB | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-6148@lists.php.net to get a copy of this message | ||
> From: Xavier Sosnowska [mailto:xso@ifrance.com]
> Sent: Friday, June 20, 2003 1:18 PM
>
> > All I can say is that you may want to check of the XML_Parser works
as
> > expected. Unfortunately I don't think there is a test script.
>
> I tested it on another machine and it indeed work as intended. I'll
see
> later on what was my problem on the 1st box.
>
> I still have a small problem though... I cannot put a default value if
I
> don't set the length. But I cannot set the length as there is now way
for
> me to know it. If I remove the default value, I then cannot have a
> not_null field (Parser error: "if field is "notnull", it needs a
default
> value" Byte: 825; Line: 30; Col: 3). But I need it a not_null field:
the
> field cannot be
> empty... Any way I can solve this problem?
Indeed a sneaky problem.
I don't have a quick answer for you here aside from making NULL
allowable. The problem is that I need to ensure that any change will
actually work the same on all platforms. This part of MDB is based on
Metabase. The Metabase developer took quite some time to come up with
the rules.
In the future the Manager will become more flexible so that you can
define how struct the Manager should be. Atm it aims at 100%
portability.
Regards,
Lukas