Re: [GENERAL] Upgrade from 8.2 to 8.3 & catching errors in functions

2009-10-27 Thread Pavel Stehule
2009/10/27 Joshua Berry : > On Tue, Oct 27, 2009 at 1:35 PM, Pavel Stehule > wrote: > | > | 2009/10/27 Joshua Berry : > | > Greetings, > | > > | > It seems that in Postgresql 8.2 less casting was necessary to coax the > | > backend to execute queries. > | > For example: > | > * Comparing a varcha

Re: [GENERAL] Upgrade from 8.2 to 8.3 & catching errors in functions

2009-10-27 Thread Joshua Berry
On Tue, Oct 27, 2009 at 1:35 PM, Pavel Stehule wrote: | | 2009/10/27 Joshua Berry : | > Greetings, | > | > It seems that in Postgresql 8.2 less casting was necessary to coax the | > backend to execute queries. | > For example: | > * Comparing a varchar with a numeric | > | > In 8.3, these will res

Re: [GENERAL] Upgrade from 8.2 to 8.3 & catching errors in functions

2009-10-27 Thread Pavel Stehule
2009/10/27 Joshua Berry : > Greetings, > > It seems that in Postgresql 8.2 less casting was necessary to coax the > backend to execute queries. > For example: > * Comparing a varchar with a numeric > > In 8.3, these will result in errors like this: > HINT:  No operator matches the given name and ar

[GENERAL] Upgrade from 8.2 to 8.3 & catching errors in functions

2009-10-27 Thread Joshua Berry
Greetings, It seems that in Postgresql 8.2 less casting was necessary to coax the backend to execute queries. For example: * Comparing a varchar with a numeric In 8.3, these will result in errors like this: HINT: No operator matches the given name and argument type(s). You might need to add expl