Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Actually I think the standard mandates case-folding (though to upper
> case rather than lower, i.e. the other way around)
That's how I read it too. SQL99 5.2 saith
22) The case-normal form of the of a is used for purposes such as and includi
Nico Sabbi wrote:
> yet I find disturbing that Postgres doesn't make the effort
> to respect the case specified by the user.
It does -- if you quote the names.
> If I created a field
> called "REF" why should Postgres call it "ref" in the output of queries
> if the standard doesn't specify any o
On Jan 18, 2008, at 1:14 PM, Nico Sabbi wrote:
Tom Lane ha scritto:
The SQL standard specifies that unquoted identifiers are case-
insensitive.
You're welcome to spell them as camelCase in your source code if you
feel like it, but don't expect that
Nico Sabbi wrote:
>
> Tom Lane ha scritto:
> > Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
> >
> >> After discovering that pg_get_serial_sequence behaves in a bit
> >> strange way[1] when it deals to case sensitiveness
> >>
> >
> > The SQL standard specifies that unquoted identifier
On Fri, 18 Jan 2008 13:14:33 +0100
Nico Sabbi <[EMAIL PROTECTED]> wrote:
> yet I find disturbing that Postgres doesn't make the effort
> to respect the case specified by the user. If I created a field
> called "REF" why should Postgres call it "ref" in the output of
> queries if the standard doesn
Tom Lane ha scritto:
Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
After discovering that pg_get_serial_sequence behaves in a bit
strange way[1] when it deals to case sensitiveness
The SQL standard specifies that unquoted identifiers are case-insensitive.
You're welcome to spell th
On Thu, 17 Jan 2008 19:07:59 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
> > After discovering that pg_get_serial_sequence behaves in a bit
> > strange way[1] when it deals to case sensitiveness
>
> The SQL standard specifies that unquoted identif
Ivan Sergio Borgonovo <[EMAIL PROTECTED]> writes:
> After discovering that pg_get_serial_sequence behaves in a bit
> strange way[1] when it deals to case sensitiveness
The SQL standard specifies that unquoted identifiers are case-insensitive.
You're welcome to spell them as camelCase in your sourc
After discovering that pg_get_serial_sequence behaves in a bit
strange way[1] when it deals to case sensitiveness... I just
discovered that you've the same behaviour for any function... at
least in PHP.
postgresql
Versione: 8.1.11
php:
Versione: 5.2.0
eg.
create or replace function testA(out pIp
