Re: Client-requested cast mode to emulate Pg8.2 on v8.3

From: Martin Langhoff <martin(at)catalyst(dot)net(dot)nz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org, moodledev(at)catalyst(dot)net(dot)nz
Subject: Re: Client-requested cast mode to emulate Pg8.2 on v8.3
Date: 2007-11-14 05:56:06
Message-ID: 473A8DF6.6090305@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> Martin Langhoff <martin(at)catalyst(dot)net(dot)nz> writes:
>> I say they are worrying because Moodle code has many ocurrences of
>> /* bla.id is an INT8 */
>> SELECT x,y,z FROM bla WHERE id='1';
>> And we also often quote INT values for inserts/updates, I am not sure if
>> this is supported either.
>
> This is not a problem. Read up on unknown-type literals --- that
> behavior isn't changing.

Tom,

thanks for the clarification - reading up on those now...

> The cases that we are tightening up on
> involve values that are of *known* non-string data types being used
> in situations where logically only a string should appear.

Hmmm. We'll have to test and see if we have any in Moodle.

- Is there a way to turn it back to the old behaviour with a
warning going to the logs?

- Is there a way to get v8.2.x to warn on the dubious casts
so we can tighten the application side while on v8.2?

cheers,

martin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message froast 2007-11-14 07:16:48 how should I do to disable the foreign key in postgres?
Previous Message Tom Lane 2007-11-14 05:37:26 Re: [HACKERS] plperl and regexps with accented characters - incompatible?