31.03.2010 12:03, A.L.E.C wrote: > Vladislav Bogdanov wrote: > >> If we simply add 'addressbook_id' field to 'contacts' table (and one >> more table with names and flags of that address books) then we can have >> as many SQL address books as one may wish. Personal addresses >> (read/write/delete/search/group), collected addresses >> (read/move/delete), imported addresses (read-only), etc. etc. And all >> insert/delete operations whould be replaced with one SQL update >> operation if user wants to move address to different addressbook. >> Groups support would be limited to address books with 'groupable' flag >> set or whatever else. > > Now I understand. So, it's just the internal structure > extension/optimization. There will be still two beings: addressbook and > group. >
Mainly - yes. But addressbook will not be limited to be the only one. And I think that allowed operations would be stored in SQL on per-book basis. And they should be extend-able. One more possible flag for future (syncml integration) whould be 'synchronizable' (personally I do not want all addresses from my address books to be synchronized with my phone). _______________________________________________ List info: http://lists.roundcube.net/dev/
