The following bug has been logged online:
Bug reference: 2059
Logged by: Chris Storah
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux - Fedora Core 4 x86_64 version
Description:PGConnect fails when used in a thread
Details:
fe
On Friday 19 Oct 2001 9:33 pm, Joel Burton wrote:
> On Fri, 19 Oct 2001, Chris Storah wrote:
> > MS SQL is set to quote all identifiers so the queries are sent in the
> > ...
Sorry about that, I wasn't clear about the quoting.
MS SQL was set to quote all identifiers so th
Just searched the archives but no match for this problem that I can see:
Exporting an MS SQL 2000 table to PostgreSQL 7.1.3 fails due to uppercase
table names.
MS SQL is set to quote all identifiers so the queries are sent in the format:
'create table TEST(ABC int)'
However, when MS SQL sends a
-
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Chris Storah" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, May 15, 2001 5:00 PM
Subject: Re: [BUGS] socket slowdown using libpg and 7.1.1 ?
> Chris Storah <[EMAIL PROTECTED]> writes:
> > A
Are there any problems with 7.1.1 when using libpg and TCP/IP socket
connections?
I have three machines, two with 7.1.1 and the other with 7.0.3.
The 7.1.1 machines are 40 times slower than the 7.0.3 machine at returning
the result sets.
I haven't included a query example/data as it is happening
st had a one-off case that confused me...ISO dates
solve
the problem though.
Thanks for the help,
Chris
- Original Message -
From: "Thomas Lockhart" <[EMAIL PROTECTED]>
To: "Chris Storah" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, May
the parser
calculating the 'best-fit' case?
Chris
- Original Message -
From: "Thomas Lockhart" <[EMAIL PROTECTED]>
To: "Chris Storah" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, April 27, 2001 5:04 PM
Subject: Re: 7.1 euro-style
7.0.x okay, 7.1 incorrect (CVS from 24th April):
create table test(aaa date);
insert into test(aaa) values ('23.10.1997');
insert into test(aaa) values ('13.10.1997');
insert into test(aaa) values ('2.10.1997');
select * from test;
gives:
a
1997-10-23
1997-10-13
1997-2-10
Automati
7.0.x okay, 7.1 incorrect (CVS from 24th April):
create table test(aaa date);
insert into test(aaa) values ('23.10.1997');
insert into test(aaa) values ('13.10.1997');
insert into test(aaa) values ('2.10.1997');
select * from test;
gives:
a
1997-10-23
1997-10-13
1997-2-10
Automati
Peter Eisentraut wrote:
>But since the problematic word in your case is not CALL but SELECT, I can
>tell you right away with relative certainty that it will not be possible
>to change the parser to accept SELECT as an identifier in all contexts
>without butchering the grammar beyond reason.
Just
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: 15 February 2001 15:23
To: Chris Storah
Cc: [EMAIL PROTECTED]
Subject: Re: [BUGS] create table bug with reserved words?
Chris Storah <[EMAIL PROTECTED]> writes:
> Is this a bug - should the parser cope with any reserved
There seems to be an inconsistency in the parsing of create table (possibly
other SQL syntax?):
create table test (call int, end, int, select int);
Fails with ERROR: parser: parse error at or near "create"
create table test (call int, end1, int, select1 int);
Works.
Call, End an
12 matches
Mail list logo
