Re: database constraints

> This brings up an interesting idea. What if it were possible to set
> some kind of rules on DDL at database creation time? For example, I'd
> like to be able to throw an error if somebody tries to name an object
> any of the SQL keywords.
>
> Other possible rules:
>
> * Every table must have a comment
> * noCamelCaps
> * downcase all entities
> * underbar_separators_required
> * abbrev_w_beg, nt_by_rmvng_vwls
> * Your favorite algorithmic coding standard here

Hmmm.. like a PostgreSQL syntax mode... in the PostgreSQL.conf:

syntax_mode = lazy, standard, strict

Where lazy is the current , standard would throw exceptions if you try
to use a reserved word or use uppercase, and strict would do things like
force a comment.

Ooooh... Bastard Operator From Hell here we come.

Sincerely,

From a managerial perspective I like it... Just like you have to be
explicit when using cvs or subversion to NOT comment.

Sincerely,

Joshua D. Drake

>
> What do y'all think?
>
> Cheers,
> D

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL