Perhaps I'm missing something here, but it looks like I'm getting an
insert into both the parent and child tables when my RULE's where
clause is based on a DEFAULT generated from a sequence. It looks like
nextval on the sequence is called 3 times for every insert.
I don't know if this is properly
The following bug has been logged online:
Bug reference: 2538
Logged by: John Lyssy
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Windows 2003 Server
Description:Hang on insert/select
Details:
Client application hangs on doing insert a
The following bug has been logged online:
Bug reference: 2535
Logged by: Marius Žalinauskas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Windows XP Pro
Description:Unicode on Windows: aogonek is not distinguished from
agrave
Details:
"Andrew Hammond" <[EMAIL PROTECTED]> writes:
> Rules:
> t2_part AS
> ON INSERT TO t2
>WHERE new.id > 10 DO INSTEAD INSERT INTO t2_child (id, name)
> VALUES (new.id, new.name)
"new.id" is replaced by "nextval('t2_id_seq'::regclass)" each time it
appears ... which will be four separat
Hi,
Recently, I had some problems with queries using the XML2 module. I was able
to reproduce the odd results using the following commands:
DROP TABLE tag CASCADE;
CREATE TABLE tag ( id SERIAL PRIMARY KEY, data TEXT );
INSERT INTO tag ( data ) VALUES ( 'anything' );
SELECT id, data FROM tag WHE
For the record: the original BUG #2535 report should be viewed in UTF-8 to see
inserted values.
--
Marius Zalinauskas
> The following bug has been logged online:
>
> Bug reference: 2535
> Logged by: Marius Žalinauskas
> Email address: [EMAIL PROTECTED]
> PostgreSQL version:
The following bug has been logged online:
Bug reference: 2539
Logged by: David Fetter
Email address: [EMAIL PROTECTED]
PostgreSQL version: All
Operating system: Linux and OSX that I've tested
Description:PL/PgSQL doesn't disallow COPY commands on compile, even
though
"David Fetter" <[EMAIL PROTECTED]> writes:
> Description:PL/PgSQL doesn't disallow COPY commands on compile, even
> though it disallows them.
There are many many things that won't be checked until execution.
I can't get excited about this one.
regards, tom lane
--
On Wed, Jul 19, 2006 at 07:02:15PM -0400, Tom Lane wrote:
> "David Fetter" <[EMAIL PROTECTED]> writes:
> > Description:PL/PgSQL doesn't disallow COPY commands on
> > compile, even though it disallows them.
>
> There are many many things that won't be checked until execution. I
> can't get
