Basically the most important thing as I see it is that we come up with a
standard we all like and stick to it.
If something along the lines of attr_name, value stored within one table
is to be used then I think agreeing that that table will store data in a
vCard format is really essential otherwise it will be impossible for
applications to interact IE how will the mail program know what format
the manager is using.
It makes a lot of sense having the person_id and name separated into a
different table. it will make searching easier and faster.
If we go with using a config schema there are also a few rules that will
need creating to identify the program using the configuration settings
.. While some settings will be global to all gpe programs and or all
contact managers. It is nesserserry to identify those values and store a
list of there naves somewhere that developers can access.
When it comes to config values dedicated to your own program it should
be simple to have a program name within the configuration table this
name would be blank for global config options or contain your project
name in lower case. It becomes very easy then to create a gpe_uninstall
script that removes all non global data when and if your app is removed
from the system.
create table gpe_config_data(
program_name text,
attribute_name text NOT NULL,
attribute_value text,
PRIMARY_KEY (program_name, attribute_name)
)
Received on Thu Jun 06 17:20:38 2002
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:41:28 EDT