Re: [HACKERS] set constraints docs page

2003-09-04 Thread Bruce Momjian
Kevin Brown wrote: > Bruce Momjian wrote: > > > Added to TODO: > > > > * Print table names with constraint names in error messages, or make > > constraint names unique within a schema > > > Should the TODO also include adding "ALTER TABLE x ALTER CONSTRAINT > y RENAME TO z" functiona

Re: [HACKERS] set constraints docs page

2003-09-04 Thread Kevin Brown
Bruce Momjian wrote: > Added to TODO: > > * Print table names with constraint names in error messages, or make > constraint names unique within a schema Should the TODO also include adding "ALTER TABLE x ALTER CONSTRAINT y RENAME TO z" functionality if we don't make constraint na

Re: [HACKERS] set constraints docs page

2003-09-04 Thread Bruce Momjian
Kevin Brown wrote: > Bruce Momjian wrote: > > Kevin Brown wrote: > > > The two approaches aren't necessarily mutually exclusive (though SQL99 > > > compliance on constraint names would obviously make it unnecessary to > > > specify a tablename along with a constraint name), so I see little > > > pr

Re: [HACKERS] set constraints docs page

2003-08-27 Thread Kevin Brown
Bruce Momjian wrote: > Kevin Brown wrote: > > The two approaches aren't necessarily mutually exclusive (though SQL99 > > compliance on constraint names would obviously make it unnecessary to > > specify a tablename along with a constraint name), so I see little > > problem here. But the current ar

Re: [HACKERS] set constraints docs page

2003-08-26 Thread Bruce Momjian
Kevin Brown wrote: > Tom Lane wrote: > > "Andrew Dunstan" <[EMAIL PROTECTED]> writes: > > >> I object to creating gratuitous incompatibilities with the SQL standard, > > >> which will obstruct legitimate features down the road. The SQL standard > > >> says it is .. > > > > > Is there a case for e

Re: [HACKERS] set constraints docs page

2003-08-19 Thread Kevin Brown
Tom Lane wrote: > "Andrew Dunstan" <[EMAIL PROTECTED]> writes: > >> I object to creating gratuitous incompatibilities with the SQL standard, > >> which will obstruct legitimate features down the road. The SQL standard > >> says it is .. > > > Is there a case for enforcing uniqueness on constraint

Re: [HACKERS] set constraints docs page

2003-08-19 Thread Stephan Szabo
On Tue, 19 Aug 2003, Peter Eisentraut wrote: > Christopher Kings-Lynne writes: > > > > > It's a constraint name. IIRC, it happens to affect all such named > > > > constraints currently. We should probably allow . > > > > (and ..) as well. Too late for 7.4, but > > > > this can happen for 7.5 if

Re: [HACKERS] set constraints docs page

2003-08-19 Thread Tom Lane
"Andrew Dunstan" <[EMAIL PROTECTED]> writes: >> I object to creating gratuitous incompatibilities with the SQL standard, >> which will obstruct legitimate features down the road. The SQL standard >> says it is .. > Is there a case for enforcing uniqueness on constraint names, then? Other than "S

Re: [HACKERS] set constraints docs page

2003-08-19 Thread Andrew Dunstan
- Original Message - From: "Peter Eisentraut" <[EMAIL PROTECTED]> To: "Christopher Kings-Lynne" <[EMAIL PROTECTED]> Cc: "Stephan Szabo" <[EMAIL PROTECTED]>; "Hackers" <[EMAIL PROTECTED]> Sent: Tuesday, August 1

Re: [HACKERS] set constraints docs page

2003-08-19 Thread Peter Eisentraut
Christopher Kings-Lynne writes: > > > It's a constraint name. IIRC, it happens to affect all such named > > > constraints currently. We should probably allow . > > > (and ..) as well. Too late for 7.4, but > > > this can happen for 7.5 if there aren't any objections. > > > > I object. > > Thanks

Re: [HACKERS] set constraints docs page

2003-08-19 Thread Christopher Kings-Lynne
> > It's a constraint name. IIRC, it happens to affect all such named > > constraints currently. We should probably allow . > > (and ..) as well. Too late for 7.4, but > > this can happen for 7.5 if there aren't any objections. > > I object. Thanks for the helpful objection. To what do you objec

Re: [HACKERS] set constraints docs page

2003-08-19 Thread Peter Eisentraut
Stephan Szabo writes: > It's a constraint name. IIRC, it happens to affect all such named > constraints currently. We should probably allow . > (and ..) as well. Too late for 7.4, but > this can happen for 7.5 if there aren't any objections. I object. -- Peter Eisentraut [EMAIL PROTECTED] -

Re: [HACKERS] set constraints docs page

2003-08-14 Thread Tom Lane
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes: > I notice on the SET CONSTRAINTS doc page, it says SET CONSTRAINTS > ... > But it doesn't at all make it clear what is, since cosntraint > names are per-relation I thought? Looking at the code, it will set the mode for *all* FKs with the sam

Re: [HACKERS] set constraints docs page

2003-08-14 Thread Stephan Szabo
On Wed, 13 Aug 2003, Christopher Kings-Lynne wrote: > Hi, > > I notice on the SET CONSTRAINTS doc page, it says SET CONSTRAINTS > ... > > But it doesn't at all make it clear what is, since cosntraint > names are per-relation I thought? It's a constraint name. IIRC, it happens to affect all su

[HACKERS] set constraints docs page

2003-08-14 Thread Christopher Kings-Lynne
Hi, I notice on the SET CONSTRAINTS doc page, it says SET CONSTRAINTS ... But it doesn't at all make it clear what is, since cosntraint names are per-relation I thought? Chris ---(end of broadcast)--- TIP 9: the planner will ignore your desire