Re: [Gnumed-devel] Validation of data within widgits

[Jim Busser]

On Jul 19, 2004, at 10:43 PM, Karsten Hilbert wrote:
> > where for example valid postal codes vary by country...
> > [do we want that] every country
> > would need its own version of the table field constraints?
> I would assume not so.

I noticed that within the server sql directory is one called 
country.specific, but do all of these serve ONLY to insert specific 
parameters (specific valid values) pertinent to the country?

Is there anywhere an overview description of how it is proposed to do 
"schema localization" if it involves a plan to do achieve or support 
anything beyond the above?

For example it would be nice to be able to require Canadian postal 
codes to satisfy A9A 9A9 and for other countries' postal codes to 
satisfy something else. Is it desirable to have these be postgres 
constraints and could they be achieved by calling/running "accessory" 
sql files as part of database creation? Or must such statements be 
tightly coupled to (or immediately follow) the lines that originally 
create the tables?

Or is there a better way, for example if the gui were to validate based 
on resources (reference files or tables) in the client directory?