> -----Original Message-----
> From: Constantin Stefanov [mailto:cstef(at)mail(dot)ru]
> Sent: 09 February 2004 09:03
> To: Andreas Pflug
> Cc: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Indexes generated for primary
> key are not show
> Why should such duplication be avoided? There is both
> constraint (primary key) and index.
Because if any generated SQL contains both object, it will be an invalid
script, not to mention the fact that you cannot properly recreate
constraints just by recreating the indexes.
> Constraint is something
> logical, index is a way to implement it. When I 'connect' a
> trigger to a table, there is trigger as a function, and
> trigger usage for a table. Yes, index is more tightly
> connected with its table, but in a case of a constraint it is
> still an index but system-generated.
Yes, which is exactly why it's hidden - in the same way we hide the
rules that implement views.
> And if it would be an option to show such indexes, such
> duplication is not a problem at all - if you turn this option
> on (it may be off by default), you know what you are doing
> and know that some constraints may be duplicated as indexes.
There speaks someone who doesn't provide support on these lists :-)
It will be a problem. People would switch on such an option whilst
playing and forget about it. We would then get lots of emails.
pgadmin-support by date
|Next:||From: Andreas Pflug||Date: 2004-02-09 10:09:44|
|Subject: Re: F2 key not working for editing rows on XP|
|Previous:||From: Constantin Stefanov||Date: 2004-02-09 09:03:25|
|Subject: Re: Indexes generated for primary key are not show|