Title: Message
Hi
Donald, sorry for the delay in replying to this fun little
bug.
It's
now fixed, and I've updated the snapshot binary for pgSchema.dll in the binaries
folder on http://cvs.pgadmin.org.
You
might want to hang on a minute before updating though as I'm about to look at
th
Title: Message
Thanks for that Dave,
I don't mind it not displaying the
constraint as an index but the one thing I would ask for is
consistency...
For example if I create the following table via
SQL:
CREATE TABLE public.tbl_cmpycat (
id int4 NOT NULL,
s_desc text NOT NULL,
id_editedby i
When I open psAdminII (1.4.12), I see listed a number of schemas which I
don't expect, namely pg_temp_1, pg_temp_2, pg_temp_3, etc., along with the
public schema, which I expect to be there.
What's up with that?
They all are "empty", in that the drill-down listing of Aggregates,
Domains, Function
Title: Message
Hi
Donald,
This
is a feature, not a bug :-)
Seriously, pgAdmin figures out that the index is part of a constraint and
classes it as a system object, therefore hiding it. If you switch on View System
Objects on the View menu, you will see both indexes under the table. My gu
Title: Message
It's a
bit bizarre I know, but it comes from some old code that had to figure out if an
index is system generated. The rules are:
1)
Unique = True AND Name = TableName_FirstColName_key (i.e. created as a unique
constraint)2) Primary = True (i.e. created as a primary key on a
> -Original Message-
> From: Berend Tober [mailto:[EMAIL PROTECTED]]
> Sent: 21 January 2003 13:40
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-support] Anomolous schemas
>
>
> When I open psAdminII (1.4.12), I see listed a number of
> schemas which I don't expect, namely pg_temp_1, pg
