From: Jean Louis <bugs@gnu.support>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: exported contacts problem
Date: Fri, 2 Aug 2019 23:34:21 +0200 [thread overview]
Message-ID: <20190802213421.GZ17561@protected.rcdrun.com> (raw)
In-Reply-To: <87mugrb7fi.fsf@ericabrahamsen.net>
* Eric Abrahamsen <eric@ericabrahamsen.net> [2019-08-02 23:11]:
> > Neither bbdb nor Org is suitable for any serious collection of
> > contacts. I have 192,000+ contacts, and when they are in database and
> > I am using PostgreSQL, it gives me most of benefits, I can sort people
> > into lists, groups, I can contact them, count interactions, open up
> > their files, emails with a fast command, edit their data, add notes,
> > send them faxes and SMS, maintain relations.
>
> That sounds pretty intense. Have you written a separate package for
> interacting with the database?
I wrote few generic functions and use it with helm, it works for
me. It is not ready for public. Web interface works based on Gedafe[1]
and then I wrote access to it through console Common Lisp and then
also through Emacs Lisp.
I am using Emacs module `emacs-libpq'[2] to interact with PostgreSQL.
Let's say I am looking for somebody, Hyper-C asks me for query, I
enter something, then I can choose to open Org file relating to the
person. When dealing with various companies, things related to a
company shall be in the directory related to company. Things related
to person, for example assignments related to one person shall be in
the file belonging to that person.
That way full file can be sent to the person for review, it becomes
clear what has been done, and what is yet to be done.
Mixing assignments, TODO, agendas from all subjects, groups and
persons into one file would give me terrible confusion.
Jean
Footnotes:
[1] https://gedafe.github.io/index.en.html
[2] https://github.com/anse1/emacs-libpq#start-of-content
next prev parent reply other threads:[~2019-08-02 21:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 15:47 exported contacts problem Jude DaShiell
2019-08-02 16:00 ` Jean Louis
2019-08-02 16:02 ` Jean Louis
2019-08-02 16:06 ` Jude DaShiell
2019-08-02 21:09 ` Eric Abrahamsen
2019-08-02 21:34 ` Jean Louis [this message]
2019-08-03 0:26 ` Eric Abrahamsen
2019-08-03 10:33 ` Jean Louis
2019-08-03 15:38 ` Eric Abrahamsen
2019-08-03 16:32 ` Jean Louis
2019-08-03 17:48 ` Neil Jerram
2019-08-03 18:25 ` Jean Louis
2019-08-03 21:32 ` Eric Abrahamsen
2019-08-03 22:12 ` Jean Louis
2019-08-04 1:28 ` Tim Cross
2019-08-13 22:24 ` David Masterson
2019-08-14 20:38 ` Eric Abrahamsen
2019-08-16 0:07 ` David Masterson
2019-08-03 10:48 ` Jean Louis
2019-08-02 22:19 ` John Kitchin
2019-08-02 20:33 ` Tim Cross
2019-08-02 20:57 ` Jude DaShiell
2019-08-02 21:25 ` Tim Cross
2019-08-02 21:39 ` Jean Louis
2019-08-02 22:07 ` Tim Cross
2019-08-03 8:25 ` Jean Louis
2019-08-02 21:00 ` Jean Louis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190802213421.GZ17561@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).