Randall Smith wrote:
> Thanks Tom. I understand your points and I gather that the cost of
> making the change (even as an option) outweighs the benefits of SQL
> conformance for the developers. Though I'm still of the same opinion.
>
> I'll give the pghackers forum a visit and since I'm alread
Randall Smith wrote:
>>> Are there plans to make Postgresql's behavior SQL compliant with
regards
>>> to quoted identifiers? My specific need is to access tables named
in
>>> lower case by an uppercase quoted identifier, which is in line with
the
>>> SQL standard.
>>
>> You must not change the
- Original Message -
From: "Randall Smith" <[EMAIL PROTECTED]>
I'll give the pghackers forum a visit and since I'm already on the subject
here, I'll make a direct comparison of the situation. Microsoft's Internet
Explorer web browser is known to have poor support for the CSS standard
Thomas Kellerer wrote:
Randall Smith wrote on 14.03.2007 18:59:
I'm trying to get Postgresql to work with software that uses JDBC and
Oracle for a large government project. So I have to report that the
application won't work with Postgresql because it (PG) doesn't adhere
to the standard. Tha
This is the last statement I found on the issue, which is someone hopeful.
http://archives.postgresql.org/pgsql-hackers/2006-11/msg00347.php
Randall
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
Randall Smith wrote on 14.03.2007 18:59:
I'm trying to get Postgresql to work with software that uses JDBC and
Oracle for a large government project. So I have to report that the
application won't work with Postgresql because it (PG) doesn't adhere to
the standard. That's usually something I
Tom Lane wrote:
Randall Smith <[EMAIL PROTECTED]> writes:
I'm an advocate of Postgresql and usually tout SQL compliance as a
strength, so it bothers me that this is not in line to be corrected.
It's not that it's not on the radar screen, it's just that no one sees
a way to do it that's going t
Randall Smith <[EMAIL PROTECTED]> writes:
> I'm an advocate of Postgresql and usually tout SQL compliance as a
> strength, so it bothers me that this is not in line to be corrected.
It's not that it's not on the radar screen, it's just that no one sees
a way to do it that's going to be acceptable
Albe Laurenz wrote:
Randall Smith wrote:
Are there plans to make Postgresql's behavior SQL compliant with
regards
to quoted identifiers? My specific need is to access tables named in
lower case by an uppercase quoted identifier, which is in line with
the
SQL standard. So if I created table
Randall Smith wrote:
> Are there plans to make Postgresql's behavior SQL compliant with
regards
> to quoted identifiers? My specific need is to access tables named in
> lower case by an uppercase quoted identifier, which is in line with
the
> SQL standard. So if I created table foo, I should b
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Are there plans to make Postgresql's behavior SQL compliant with regards
> to quoted identifiers?
No.
> My specific need is to access tables named in lower case by an uppercase
> quoted identifier, which is in line with the SQL standard.
Are there plans to make Postgresql's behavior SQL compliant with regards
to quoted identifiers? My specific need is to access tables named in
lower case by an uppercase quoted identifier, which is in line with the
SQL standard. So if I created table foo, I should be able to access it
like "FO
12 matches
Mail list logo
