hi,
Dan Field wrote:
I've stumbled across a query I don't quite understand the error message
for.
This query is pulled from a working MySQL setup:
SELECT
DEWEY_ID, DEWEY_HUNDREDS, DEWEY_TENS, DEWEY_ONES,
DEWEY_POINT_ONES, DEWEY_POINT_TENS,
DEWEY_POINT_HUNDREDS, DEWEY_POINT_THO
On Sun, Apr 18, 2004 at 20:24:47 +0100,
Paul Thomas <[EMAIL PROTECTED]> wrote:
>
> PostgreSQL can be coerced into accepting where foo = null with the
> transform_null_equals run-time option but that doesn't make it legal SQL
> IFAIK.
foo = NULL is a valid SQL expression that always returns NU
On 18/04/2004 19:37 Markus Bertheau wrote:
В Чтв, 15.04.2004, в 13:15, Paul Thomas пишет:
> On 15/04/2004 11:25 Dan Field wrote:
> Your "= NULL" tests are also not valid SQL (should be IS NULL).
I think = NULL _is_ valid SQL, it just doesn't do what you think.
It's valid in an assignment
update
Ð ÐÑÐ, 15.04.2004, Ð 13:15, Paul Thomas ÐÐÑÐÑ:
> On 15/04/2004 11:25 Dan Field wrote:
> Your "= NULL" tests are also not valid SQL (should be IS NULL).
I think = NULL _is_ valid SQL, it just doesn't do what you think.
--
Markus Bertheau <[EMAIL PROTECTED]>
---(end of b
El Jue 15 Abr 2004 07:25, Dan Field escribió:
> I've stumbled across a query I don't quite understand the error message
> for.
>
> This query is pulled from a working MySQL setup:
>
> SELECT
> DEWEY_ID, DEWEY_HUNDREDS, DEWEY_TENS, DEWEY_ONES, DEWEY_POINT_ONES,
> DEWEY_POINT_TENS,
>
On 15/04/2004 11:25 Dan Field wrote:
I've stumbled across a query I don't quite understand the error message
for.
This query is pulled from a working MySQL setup:
SELECT
DEWEY_ID, DEWEY_HUNDREDS, DEWEY_TENS, DEWEY_ONES,
DEWEY_POINT_ONES, DEWEY_POINT_TENS, DEWEY_POINT_HUNDREDS,
DEWEY_POIN
On Thu, Apr 15, 2004 at 11:25:59AM +0100, Dan Field wrote:
> I've stumbled across a query I don't quite understand the error message
> for.
>
> This query is pulled from a working MySQL setup:
>
> SELECT
> DEWEY_ID, DEWEY_HUNDREDS, DEWEY_TENS, DEWEY_ONES, DEWEY_POINT_ONES,
> DEWEY_POINT_
