Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tom Lane wrote:
> Martin Langhoff <martin@xxxxxxxxxxxxxxx> 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

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux