In phpPgAdmin, we list them separately as well, however it did require some thinking. In the end I decided to display things in the way the SQL spec lays them out. All constraints together, etc.
And do you display indexes which are automatically generated by PRIMARY
KEY constraint?
No. The index name is same as constraint name anyway. But we've never had anyone complain about it yet.
I would not say those indexes should be in generated SQL
- they certainly should not. But I say those indexes should be displayed where user-created indexes are. Dave says they shouldn't - well, he is a developer of PgAdmin, and I will use PgAdmin whether this feature will be implemented or not, it is useful and convenient tool. But I asked for it because in my opinion it will make PgAdmin more convenient. The final desicion is, of course, made by developers, I only try to convince them that my suggestion makes sense.
It does, but it also adds weirdness, because the same thing is listed in two different places. I'd consider adding them to the phpPgAdmin index view as sort of greyed out maybe, and under a heading 'constraint indexes'
Chris
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
