Обсуждение: Schema for J2EE project
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?
Will using a schema other than public cause problems for users accessing the database with ODBC from Windows?
Thank you,
Margaret.
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?
Will using a schema other than public cause problems for users accessing the database with ODBC from Windows?
Thank you,
Margaret.
MargaretGillon@chromalloy.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