The comment I have from Tom Lane on this patch is:
band-aid solution to just one aspect of problem ...
so I am afraid I am going to have to reject it. Sorry.
---
Mark Kirkwood wrote:
> I encountered this bug recen
Added to TODO:
* Fix inconsistent precedence of =, >, and < compared to <>, >=, and <=
http://archives.postgresql.org/pgsql-bugs/2007-12/msg00145.php
---
Pedro Gimeno wrote:
> Tom Lane wrote:
>
> > "Kevin Grittner" <[E
I am discarding this thread from the patches queue. We have fixed some
of it so a LOG message is issued for invalid postgresql.conf
combinations. We could do more, but there doesn't seem to be a clear
TODO here.
---
Tom Lan
On Fri, Mar 21, 2008 at 7:00 PM, IP <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4048
> Logged by: IP
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3.0
> Operating system: Windows XP PL SP2
> Description:
The following bug has been logged online:
Bug reference: 4048
Logged by: IP
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: Windows XP PL SP2
Description:Can't install pltcl
Details:
-- Executing query:
CREATE LANGUAGE plpythonu;
Query
SELECT "Id" AS ID
and this will return 'id' instead of 'ID'
may be is there server configurations variable to be case sensitive?
or return case preserved field names?
or may be I compile manually PostgreSQL to do that?
Because typing SELECT "Id" AS "ID" instead of SELECT ID is boring
else more y
<[EMAIL PROTECTED]> writes:
> It is have no any matter to me if it is upshifted or lowershifted on server
> sidethe standard does not specify that output of queries MUST be
> lowershifted/upshifted.
Yes it does. I quote SQL92 section 5.2 syntax rule 10:
The of a is equivalent
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
It is have no any matter to me if it is upshifted or lowershifted on server
sidethe standard does not specify that output of queries MUST be
lowershifted/upshifted.why you do this?
http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php
- Original Message -
From: "John R Pi
It is have no any matter to me if it is upshifted or lowershifted on server
sidethe standard does not specify that output of queries MUST be
lowershifted/upshifted.why you do this?- Original Message -
From: "John R Pierce" <[EMAIL PROTECTED]>
To: "Eugen Konkov" <[EMAIL PROTECTED]>
Cc:
Eugen Konkov wrote:
Is there any workaround other then quoting to get working 1) and 2) as
expected?
The SQL standard actually says everything not quoted should be upshifted
to upper case. PostgreSQL opted for lower case a long time ago and has
stuck with this for legacy.
If your "100K
The following bug has been logged online:
Bug reference: 4047
Logged by: Eugen Konkov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: Windows XP
Description:case preserve for columns
Details:
1)
SELECT Id FROM MYTABLE;
$sth= fetchall_hashr
12 matches
Mail list logo
