From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: exported contacts problem Date: Sat, 03 Aug 2019 08:38:15 -0700 Message-ID: <874l2yxnrs.fsf@ericabrahamsen.net> References: <20190802160236.GR17561@protected.rcdrun.com> <87mugrb7fi.fsf@ericabrahamsen.net> <20190802213421.GZ17561@protected.rcdrun.com> <875znfaycd.fsf@ericabrahamsen.net> <20190803103340.GN23820@protected.rcdrun.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:60904) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1htw70-0008Qh-52 for emacs-orgmode@gnu.org; Sat, 03 Aug 2019 11:38:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1htw6y-0005Vc-Ra for emacs-orgmode@gnu.org; Sat, 03 Aug 2019 11:38:26 -0400 Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:55100 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1htw6y-0005V7-Kq for emacs-orgmode@gnu.org; Sat, 03 Aug 2019 11:38:24 -0400 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1htw6w-000ryv-7K for emacs-orgmode@gnu.org; Sat, 03 Aug 2019 17:38:22 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Jean Louis writes: > * Eric Abrahamsen [2019-08-03 02:27]: >> Okay, thanks for that run-down, pretty interesting. I've written a >> package called EBDB[1] that's meant to be sort of an update to BBDB, and >> while I think someone's using it with tens of thousands of contacts, >> 192k records would probably exhaust it. It has pluggable data stores, >> however, one of which will (eventually) be a proper external database, >> so I'm always interested in how people are using this stuff. >> >> Eric >> >> [1] https://github.com/girzel/ebdb > > I have tried it. It has good concepts and integration. But I cannot > switch to it. No, and I think it would fall apart under your workload. But I would like to make it better, and gradually get it closer to supporting the sort of thing you're doing. > Please, if you intend to make vcard import, don't make vcard stuff > bundled with the ebdb, you will make repeated mistake. > > Make one vcard import package that give elisp structure, something > like hash or alist, plist, whatever is better. Yes, that's on my (mid-length) list of to do: a vcard parsing library that just turns vcards into a couple pre-defined formats, or lets you register your own consumption functions. > Then such package is best to contribute to GNU Emacs. > > Then all other packages can use vcard import. > > This makes much sense rather than making it single-package oriented. > > I don't think that vCard complexity is necessary for contacts, > standard is invented, but is too complex. But if you are doing it, > than such feature can contribute to overall usage. I'm also not fond of vcard, but I *am* fond of carddav, and having my contacts synced to my phone, and shared with co-workers, etc. Otherwise I probably wouldn't bother. Jean Louis writes: > * Eric Abrahamsen [2019-08-03 02:27]: >> Okay, thanks for that run-down, pretty interesting. I've written a >> package called EBDB[1] that's meant to be sort of an update to BBDB, and >> while I think someone's using it with tens of thousands of contacts, >> 192k records would probably exhaust it. It has pluggable data stores, >> however, one of which will (eventually) be a proper external database, >> so I'm always interested in how people are using this stuff. >> >> Eric >> >> [1] https://github.com/girzel/ebdb > > Not sure if you rely on vCard as some kind of "standard". It is > attempt to globalize the contact keeping, but I don't find it good, > not at all. > > It is way too complicated. It tries to encompass everything possible > in one file, file which is probably not related to other files at all. > > Only relational database makes sense for complex contact management. EBDB now provides for a sort of poor-man's relational database, with multiple "roles" and relations, linking people to people and people to organizations. But it's still limited and kind of awkward. Eric