From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | MargaretGillon(at)chromalloy(dot)com |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Schema for J2EE project |
Date: | 2009-03-31 08:34:57 |
Message-ID: | 49D1D5B1.9020906@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
MargaretGillon(at)chromalloy(dot)com wrote:
> Using Postgresql 8.2.11 on Ubuntu 7.10.
>
> I am writing a J2EE project but do not want user specific schemas because this
> application sits on a production floor and any production employee can walk to a
> workstation and access the database to punch work time. I know that the public
> schema is not supposed to be used.
>
> Is the best practice to make one schema for the database and then delete public?
One or more. I use schemas to group tables and functions by usage
(lookups, util, system) as well as to provide permission control.
> Will using a schema other than public cause problems for users accessing the
> database with ODBC from Windows?
Shouldn't, but iirc you'll need to explicitly specify <schema>.<table>
rather than relying on search_path.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Stuart Bishop | 2009-03-31 09:17:10 | Re: Re: [GENERAL] pgstattuple triggered checkpoint failure and database outage? |
Previous Message | Thomas Pundt | 2009-03-31 07:31:24 | Re: partial TEXT search on an index |