From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgresql vs mysql |
Date: | 2007-02-22 01:42:45 |
Message-ID: | 20070222014245.GA4561@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Feb 21, 2007 at 01:45:08PM -0600, Ron Johnson wrote:
> On 02/21/07 08:42, Michael Fuhr wrote:
> > Not as good as "ERROR: hey bonehead, there ain't no such date" but
>
> But it *inserts the "data"*!!!!!
I didn't say otherwise and I'm not defending MySQL's behavior. I was
simply refuting the statement that "it doesn't warn you that it didn't
like the input format."
> > at least it's something :-)
>
> Sure, at the interactive command line.
>
> What kind of error code does this return to applications? Can a PHP
> or C programmer catch this warning, or does MySQL return a success code?
Beats me; I care about my data so I don't use MySQL. Since it's a
warning I expect the query returns success. The C API has a
mysql_warning_count() function that appears to be exposed in PHP's
mysqli extension as mysqli_warning_count. That C function doesn't
appear in the source code for any of the other MySQL extensions in
PHP 5.2.1.
--
Michael Fuhr
From | Date | Subject | |
---|---|---|---|
Next Message | Erick Papadakis | 2007-02-22 01:50:20 | Re: postgresql vs mysql |
Previous Message | Ron Johnson | 2007-02-22 01:17:16 | Re: postgresql vs mysql |