From: | Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Rename Schema Removes Unique Constraints? |
Date: | 2010-12-31 18:06:49 |
Message-ID: | AANLkTi=A_SoWhDJ_=_XhWB7f4vFwzmZGqhLKWO2dr=wi@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I decided last night to rename my 'public' schema (Not sure of that's
a good / bad idea) since I'm still learning about how schema's work on
PostgreSQL. My question is:
1. If I have a constraint (specifically 'unique') on a specific table,
when I rename the public schema, does that impact my ''unique', 'not
null', and 'primary key' constraints?
2. When you install a new PostgreSQL server at home or work, do you
guys generally leave the default 'public' schema or do you at some
point rename or use new schema for reasons I'd like to understand. I
don't understand how schema's really fit into the picture but I'm
interested in knowing what others do with their default schema.
Thanks for the help!
From | Date | Subject | |
---|---|---|---|
Next Message | bricklen | 2010-12-31 19:13:23 | Re: ERROR: could not open relation base/2757655/6930168: No such file or directory -- during warm standby setup |
Previous Message | Gordon Shannon | 2010-12-31 17:52:19 | Re: seg fault crashed the postmaster |