| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | bricklen <bricklen(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: PG wiki updated with query to show unindexed foreign keys |
| Date: | 2013-07-10 00:34:38 |
| Message-ID: | 70E06932-F26B-4528-8E33-21FFE90B6EF8@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Jul 9, 2013, at 6:29 PM, bricklen wrote:
> On Tue, Jul 9, 2013 at 5:02 PM, Scott Ribe <scott_ribe(at)elevated-dev(dot)com> wrote:
> On Jul 7, 2013, at 5:29 PM, bricklen wrote:
>
> > Suggestions and feedback welcome on the query referenced in the link above.
>
> Lack of quoting of identifiers means that it will croak on a database that uses mixed-case identifiers.
>
> --
> Scott Ribe
> scott_ribe(at)elevated-dev(dot)com
> http://www.elevated-dev.com/
> (303) 722-0567 voice
>
> I've updated the wiki (https://wiki.postgresql.org/wiki/Unindexed_foreign_keys) to reflect your suggestion.
>
> Thanks!
Indeed ;-)
It now works on my database that carries a mixed-case naming convention from before I switched to PG (actually, from before PG existed)...
And it flagged some that I need to fix!
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bricklen | 2013-07-10 00:36:23 | Re: PG wiki updated with query to show unindexed foreign keys |
| Previous Message | bricklen | 2013-07-10 00:29:38 | Re: PG wiki updated with query to show unindexed foreign keys |