On Wed, Jan 04, 2006 at 01:36:45PM -0600, John McCawley wrote: > I have decided that I'm going to resume working on my pgDesigner project > ( http://www.hardgeus.com/projects/pgdesigner/ ). I haven't really > maintained it for over a year, but I get about 200 visits a day to the > project homepage, and about two or three emails a week asking for help. > As the project currently stands, it stores datamodel information in a > text file separate from the database. What I would like to do is modify > the application such that it can operate in "live" mode. i.e. store all > visual datamodel information in the database itself in a series of > tables. My question for this list is the following: Is there a > standard way for storing quasi-system related information in Postgres. > i.e., this is essentially an admin tool, and I was wondering if there > are naming conventions etc. I should follow such as the table names etc. > > John > It is recommended that the application data tables reside in their own schema. If the schema is not meant to be used by anything other than your program, then consider prepending the schema name with an underscore. For example: _pgdes.tablex _pgdes.tabley _pgdes.tablez Be sure you tell people that the tables are being created in their databases when you do it. elein
