[Gnumed-devel] demographic API

[Horst Herb]

I have now simplified the API proposal for demographic services to the extreme 
by returning 'dictionary type' values for all functions not returning boolean 
or just the primary key. 

Probably the only way of ensuring indefinite backwards/forwards compatibility: 
the application just needs to catch KeyError exceptions.
Dictionary keys are usually the table attributes - but even this is flexible 
by providing a "translator" method.
Objects stemming from multiple tables should be accessed via updateable views, 

Many-to-many relationships require some tweaking of the dicts (implement as 
dict of dicts)

Have a look at the draft in gnumed/test-area/hherb/gmDemographicService.py

Any major problems with this approach?

Horst