[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Questions re database schema:street:address:urb:count

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Questions re database schema:street:address:urb:country
Date: Mon, 30 Aug 2004 19:08:46 +0200
User-agent: Mutt/

> > Imagine the following scenario. At the moment gnuMed (yet in its infancy)
> > has in only a tiny part of the database over 160 tables, which read like a
> > dogs breakfast. We should be aiming to visually keep all similar data
> > together ie same sort of object heirachy that one should be using in
> > descriptive terms in the python code:
> >
> > eg    demographics_country
> >         demographics_states
> >         demographics_streets
> Almost good, but it comes better: Newer postgres versions support table name 
> spaces.
> You create a name space "demographics", and then access the table "country" 
> within that namespace via "" 
BUT they should be used sanely, eg. IMO they should represent
our "services". Still, Richard has a good point in naming
consistenly. Views already do, they all start with v_*. So do
cfg tables, they start with cfg_*. So do many clinical tables,
the start with clin_*. So do indices, they start with idx_*.

Will comment more soon.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]