On Dec 11, 2007 10:49 AM, <[EMAIL PROTECTED]> wrote:
> Will do. It might be worth noting in the loader documentation that
> mysql does this, and how it affects loader, if it isn't already there
> (it's entirely possible i missed it).
I added a brief "gotchas" section to the Loader docs in SVN.
Quoting John Siracusa <[EMAIL PROTECTED]>:
> Did you use the Loader to make these classes? MySQL tends to offer up
> empty string default values for non-null character columns, and the
> Loader dutifully reflects that, having no way to distinguish between
> "legitimate" empty string default values
On Dec 11, 2007 8:57 AM, Adam Prime <[EMAIL PROTECTED]> wrote:
> Now that i've slept i'm wondering if the underlying problem might be
> related to the way that defaults are handled in RDBO. That's one thing
> that differs between the tables used in the original tests and the table
> in the test i
Now that i've slept i'm wondering if the underlying problem might be
related to the way that defaults are handled in RDBO. That's one thing
that differs between the tables used in the original tests and the table
in the test i submitted.
Adam
[EMAIL PROTECTED] wrote:
> With this patch, every
With this patch, everything + my failing test passes. I'm not sure if
this is a good idea or a bad idea though. In my test that fails $_ is
defined as an empty string (as far as i can tell) for some reason,
instead of as undef as i would expect. There's probably an underlying
bug causing
I was crying about this on IRC this afternoon, but didn't get much of a
response, i've bashed away at it long enough to come up with a failing
test now, so maybe someone can help me out.
the attached files go like this.
t/adam_test.t
t/lib/EatLocal/DB.pm
t/lib/EatLocal/DB/Object.pm
t/lib/EatLo
