Re: [BUGS] ERROR: CreateTrigger: function check_primary_key() doesnot exist

On Thu, 19 Jul 2001 [EMAIL PROTECTED] wrote: > Young ([EMAIL PROTECTED]) reports a bug with a severity of 2 > The lower the number the more severe it is. > > Short Description > ERROR: CreateTrigger: function check_primary_key() does not exist > > Long Description > I am using 7.1.2 > > I alwa

[BUGS] ERROR: CreateTrigger: function check_primary_key() does not exist

Young ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description ERROR: CreateTrigger: function check_primary_key() does not exist Long Description I am using 7.1.2 I always got such an error when creating a trigger: ERROR: CreateTrigger

Re: [BUGS] Two foreign keys in one table both referencing same recordin primary table gives error on update of primary table

Yes, it's because it sees the intermediate state (6,1) when it shouldn't (it processes each foreign key separately and does the cascade update which places it in an "invalid" state since the 1 key no longer exists). I believe the fixes I've been working on for deferred constraints will make this

[BUGS] Two foreign keys in one table both referencing same record in primary table gives error on update of primary table

Bob Soeters ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Two foreign keys in one table both referencing same record in primary table gives error on update of primary table Long Description (PostgreSQL 7.1.1 on i686-pc-linux

Re: [BUGS] libpgtcl doesn't use UTF encoding of TCL

Reinhard Max <[EMAIL PROTECTED]> writes: > On Wed, 18 Jul 2001, Bruce Momjian wrote: >> Do you have any idea how this will work with earlier TCL versions? > It won't. If pgtcl is supposed to still be able to compile with older > versions of Tcl, the changes have to be made a compile time option.

Re: [BUGS] libpgtcl doesn't use UTF encoding of TCL

On Wed, 18 Jul 2001, Bruce Momjian wrote: > Do you have any idea how this will work with earlier TCL versions? It won't. If pgtcl is supposed to still be able to compile with older versions of Tcl, the changes have to be made a compile time option. > When was Tcl_UtfToExternalDString added to T

Re: [BUGS] Curious result from text ( netmask ( inet ) ) functions.

"Vadim I. Passynkov" <[EMAIL PROTECTED]> writes: > spidermon=# SELECT text ( netmask ( '192.168.1.1/28' ) ); > text > > 255.255.255.240/32 - ?? > (1 row) That's what it's defined to do. See http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/fun

Re: [BUGS] libpgtcl doesn't use UTF encoding of TCL

> On Wed, 18 Jul 2001, Bruce Momjian wrote: > > > Do you have any idea how this will work with earlier TCL versions? > > It won't. If pgtcl is supposed to still be able to compile with older > versions of Tcl, the changes have to be made a compile time option. Can't we probe the TCL version in

Re: [BUGS] libpgtcl doesn't use UTF encoding of TCL

Do you have any idea how this will work with earlier TCL versions? When was Tcl_UtfToExternalDString added to TCL? > Eugene Faukin ([EMAIL PROTECTED]) reports a bug with a severity of 2 > The lower the number the more severe it is. > > Short Description > libpgtcl doesn't use UTF encoding of T

[BUGS] Curious result from text ( netmask ( inet ) ) functions.

spidermon=# SELECT version(); version -- PostgreSQL 7.1.2 on i386--freebsd4.3, compiled by GCC 2.95.3 (1 row) spidermon=# SELECT netmask ( '192.168.1.1/28' ) ; netmask ---

[BUGS] libpgtcl doesn't use UTF encoding of TCL

Eugene Faukin ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description libpgtcl doesn't use UTF encoding of TCL Long Description Modern versions of the TCL (8.2 at least) use UTF encoding to internal storage of the text. libpgtcl uses T