I know this is a work in progress, but I am beginiing to wonder if it would just be easier to sync the gmail address book instead of importing it?
On Tue, Jan 12, 2010 at 6:31 PM, George Niculae <[email protected]>wrote: > > > --- On Wed, 1/13/10, Arjun Nair <[email protected]> wrote: > > > > I propose we add two columns to the phonebook_file_entry > > table, "id", and "gmail_id". For contacts imported through > > gmail, we set the "gmail_id" as the gmail address, and set > > the "id" as the resource id provided by gmail. For non-gmail > > contacts, lets use a hash of the entry-key as the "id" and > > set "gmail_id" to null. Or alternatively, instead of adding > > a "gmail_id" column, we could introduce a secondary table > > that maps "gmail_id"s to "phonebook_file_entry_id"s. What do > > you think? > > At a first thought - I think a table per class hierarchy mapping would > better fit here - we can go for a discriminator column to differentiate > gmail imported contacts from csv (kind of what we already have for schedules > - user, general and user groups) and to keep both id and gmail_id in > phonebook_file table > > George > > > > > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
