Re: Client-requested cast mode to emulate Pg8.2 on v8.3
От | Martin Langhoff |
---|---|
Тема | Re: Client-requested cast mode to emulate Pg8.2 on v8.3 |
Дата | |
Msg-id | 473A8DF6.6090305@catalyst.net.nz обсуждение исходный текст |
Ответ на | Re: Client-requested cast mode to emulate Pg8.2 on v8.3 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Client-requested cast mode to emulate Pg8.2 on v8.3
|
Список | pgsql-general |
Tom Lane wrote: > Martin Langhoff <martin@catalyst.net.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
В списке pgsql-general по дате отправления: