Re: [SQL] Approved

2003-06-06 Thread pgman
Please see the attached file. ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [SQL] To ListAdms: Is pgsql-sql operating?

2003-06-06 Thread Joerg Hessdoerfer
On Thursday 05 June 2003 18:25, you wrote: > Achilleus, > > > Is there any problem with [EMAIL PROTECTED] list? > > The mail server died on Tuesday. It's still recovering. Wow! Recovering from being dead... what a medical achievement ;-) Greetings, Joerg -- Leading SW developer - S.E.A

Re: [SQL] simulating partial fkeys.. [ATTN Developers please]

2003-06-06 Thread Richard Huxton
On Thursday 05 Jun 2003 3:55 pm, [EMAIL PROTECTED] wrote: > hi , > > Is there any way to enforce fkeys only on subset of > the table something on the lines of unique partial indexes I'm afraid not (AFAIK). What might be a solution in your case is to define another unique index. For example, you m

Re: [SQL] simulating partial fkeys..

2003-06-06 Thread Jan Wieck
[EMAIL PROTECTED] wrote: hi , Is there any way to enforce fkeys only on subset of the table something on the lines of unique partial indexes Sure. Put NULL values into the referencing fields of those rows you don't want to be checked. Jan -- #

Re: [SQL] simulating partial fkeys..

2003-06-06 Thread Bruno Wolff III
On Thu, Jun 05, 2003 at 20:25:32 +0530, [EMAIL PROTECTED] wrote: > > > hi , > > Is there any way to enforce fkeys only on subset of > the table something on the lines of unique partial indexes > > or any work around ? (on update or insert trigger is the only thing i can think of) If the fore

[SQL] simulating partial fkeys..

2003-06-06 Thread mallah
hi , Is there any way to enforce fkeys only on subset of the table something on the lines of unique partial indexes or any work around ? (on update or insert trigger is the only thing i can think of) regds mallah. - Get your free web based email at tra

[SQL] Changing owner of function -- best method?

2003-06-06 Thread Josh Berkus
Folks, I have several functions in a 7.2.4 database that I accidentally REPLACEd while logged in as the superuser, instead of the db owner. As a result, the db owner can no longer modify those functions -- they belong to the superuser. As this is a production database, I can't drop the funct