Re: [Gnumed-devel] Questions re database schema - nomenclature

[Karsten Hilbert]

> 1) NOMENCLATURE in table generating queries:
> 
>       -Given that one will be doing various joins
>        (and I'm not sure if 8.0 supports outer),
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Richard, you gotta be kidding us. Why do you think
we don't use MySQL ?

> CREATE TABLE public.country
> (
>   id_country serial NOT NULL,
>   country_code char(2) NOT NULL,
>   country_name text NOT NULL, 
>   country_deprecated date,..... etc
Never. Simply too much typing for no gain at all. PostgreSQL
already supports true namespace scoping at various levels:

qualified field names:

 country.code

alias-qualified field names:

 ... lst.code from lu_state lst ...

schema qualified table.field names:

 public.country.code

Eg. no need to invent artificial *namespaces* (this is
different from naming conventions for grouping or "typing"
objects which does make sense).

> manager), so have real life experience in the difficulties of implementing 
> and maintaining code - hence my personal insistance on good naming practices
Who would argue with that conclusion ?

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346