On 1/17/07, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> On Jan 17, 2007, at 12:56 PM, John Siracusa wrote:
>> But now that I look further, it appears that it's the "describe
>> mytable" output that's incorrect (or at least misleading). When I
>> insert a row without specifying a value for that V
On Wed, 2007-01-17 at 17:33 -0500, John Siracusa wrote:
> I was ignoring strict mode for the purposes of this exploration. Even
> in "crazy old MySQL mode" I think the "describe table" output should
> more closely match what's returned by DBD::mysql in COLUMN_DEF.
I agree, that sounds like a bug
>mysql behaves DRASTICALLY different depending on that flag. it might
>actually do what you expect it to when turned on.
>// Jonathan Vanasco
"It might actually do what you expect"... hehe...well said!
-
Take Surveys.
On Jan 17, 2007, at 12:56 PM, John Siracusa wrote:
> But now that I look further, it appears that it's the "describe
> mytable" output that's incorrect (or at least misleading). When I
> insert a row without specifying a value for that VARCHAR(10) NOT NULL
> column, it ends up with an empty strin
On 1/17/07, Cory Bennett <[EMAIL PROTECTED]> wrote:
>> This is arguably a bug in DBD::mysql, but as far as RDBO is concerned,
>
> For what it is worth, I dont think it is strictly DBD::mysql's fault, it is
> Mysql itself.
>
> http://dev.mysql.com/doc/refman/5.0/en/data-type-defaults.html
>
> It mig
On Wed, 2007-01-17 at 10:01 -0500, John Siracusa wrote:
> I'm forwarding this private email thread to the list with the
> permission of the (now anonymized) sender because it's about an
> unexpected situation that many RDBO users may face. Yes, it revolves
> around yet another fun feature of MySQL
> This is arguably a bug in DBD::mysql, but as far as RDBO is concerned,
For what it is worth, I dont think it is strictly DBD::mysql's fault, it is
Mysql itself.
http://dev.mysql.com/doc/refman/5.0/en/data-type-defaults.html
It might be fixed with mysql 5.0.2, but I do not have that version
I'm forwarding this private email thread to the list with the
permission of the (now anonymized) sender because it's about an
unexpected situation that many RDBO users may face. Yes, it revolves
around yet another fun feature of MySQL/DBD::mysql. How did you
guess? :)
Anyway, here it is, for pos
