This is expected behaviour, the 'real' code gets emitted when you OPEN
the cursor, i.e. you should be doing something like:
EXEC SQL DECLARE demo_cur CURSOR FOR
SELECT field1, field2
FROM test;
EXEC SQL OPEN demo_cur;
if( sqlca.sqlcode != 0 )
{
some_error();
return;
}
while( 1 )
piers haken ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
optimizer: convert 'IN' to join
Long Description
the optimizer should do better than a sequential scan with statements like:
SELECT * FROM t1 WHERE t1.index IN (SELEC
Is this a bug?
"Andy Marden" <[EMAIL PROTECTED]> wrote in message
news:a4u6fh$orp$[EMAIL PROTECTED]...
> Am loading date fields from text in one table to date in another. Format
of
> the text dates is 'DD.MM.YY', so that's the format mask I use. Dates for
> 2001 work OK - '02.09.01' translates as
"Andy Marden" <[EMAIL PROTECTED]> writes:
> Is this a bug?
Yes. It's fixed in 7.2 ...
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Vivek Khera <[EMAIL PROTECTED]> writes:
> "owner_lastbilled" date DEFAULT 'CURRENT_DATE' NOT NULL,
The above was never correct. I believe that 7.1's rather lax date
parser might have interpreted the literal as being 'current'. 7.2's
date parser would reject it, even if 'current' were still an
Vivek Khera <[EMAIL PROTECTED]> writes:
> Then how come pg_dump outputs it that way? Is it because that's how I
> did it when creating the schema in the first place?
Presumably.
> TL> Because it is not one: it is a datatype behavioral change.
> It isn't documented in the HISTORY file in any wa
During the upgrade from 7.1.3 to 7.2, I encountered an incompatibility
with the schema defs.
Prior to the upgrade, I used the 7.1.3 pg_dump program to create a
compressed dump:
pg_dump -Fc vk > vk.dump
then, using the 7.2 pg_restore, I exctracted the table schema
definitions:
pg_restore -l vk.
> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> Vivek Khera <[EMAIL PROTECTED]> writes:
>> "owner_lastbilled" date DEFAULT 'CURRENT_DATE' NOT NULL,
TL> The above was never correct. I believe that 7.1's rather lax date
TL> parser might have interpreted the literal as being 'current'. 7.2
Hello PostgreSQL,
I am trying to install the PostgreSQL 7.2 downloaded by Cygwin but the
install does not match any of the documentation. Help!
Last year I installed PostgreSQL 7.1 on NT for a one off project then
deleted it. I used the pg download then added Cygwin using the Cygwin
download. Eve
> Is this a bug?
> > Am loading date fields from text in one table to date in another.
> > Format of the text dates is 'DD.MM.YY', so that's the format mask
> > I use. Dates for 2001 work OK - '02.09.01' translates as
> > '2001-09-02', but '02.09.00' translates to '0001-09-02 BC'!
> > The y2k.htm
Peter <[EMAIL PROTECTED]> writes:
> I resorted to trial and error. Initdb hangs when "Creating template1
> database" so there must be a step missing.
I think you forgot to run the cygipc daemon.
regards, tom lane
---(end of broadcast)-
Do we have a workaround for 7.1.3? I don't really want to risk
an upgrade at this stage in the system
Cheers
Andy
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Andy Marden" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, February 20, 2002 11:21 PM
Subject: R
12 matches
Mail list logo
