Viacheslav N Tararin <[EMAIL PROTECTED]> writes:
> Next rule return 0 as count of changed rows but really at lest one
> record updated and one inserted
In what PG version? There's been substantial fooling-about with the
semantics of returned counts for rules in recent releases.
In any case, you
[EMAIL PROTECTED] wrote:
> Yeah, we have seen this before on various platforms. On some,
> LD_LIBRARY_PATH isn't actually anything the dynamic linker pays
> attention to, and on others, it is trumped by the installation rpath
> built into the executables. Not putting an rpath into the executables
On Mon, 6 Oct 2003, Ara Anjargolian wrote:
> Also notice that the foreign key constraint is not declared until after
> the table definition. This error does not show up if the foreign key is
> added when the content table is defined.
It works the same for me as a table constraint or as an alter
Hi.
All work as expected but...
Next rule return 0 as count of changed rows but really at lest one
record updated and one inserted
-
create or replace rule U_ENTRY
as on update to ENTRY
do instead (
update DISSECTION
set DESCRIPTION = new.DESCRIPTION,
CU
I'm using PostgreSQL 7.3.4 on cygwin
A coding error on my part revealed what appears
to be a a bug in PostgreSQL's foreign key behavior.
reduced bug-revealing code:
**
create table languages(
language_code char(2) not null,
language varchar(100) not null,
c
