From: Jean Louis <bugs@gnu.support>
To: Christopher Dimech <dimech@gmx.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Designing people and organization management for Emacs
Date: Fri, 4 Dec 2020 20:56:04 +0300 [thread overview]
Message-ID: <X8p4NOPHv3Zb8HAe@protected.rcdrun.com> (raw)
In-Reply-To: <trinity-20a8a045-3319-477b-99f3-2e767e6259f2-1607100142817@3c-app-mailcom-bs11>
* Christopher Dimech <dimech@gmx.com> [2020-12-04 19:42]:
> > In relation to this project "people" I am now polishing the table
> > unless there are no comments in the way how I think is best. Then
> > users can adapt table if they wish to or make their own functions to
> > enhance.
>
> Would need some useful description of making new tables and some functions
> that would help users do that. At least spare them some of the process.
When preparing Emacs package let us say for people's contact
management then users do not need to think much of the underlying
database table design. They think of people's names, birthdate,
address, and contact information.
Programmers need to know how to make functions or do SQL queries.
Some references:
https://aiven.io/blog/an-introduction-to-postgresql
https://www.postgresqltutorial.com/
next prev parent reply other threads:[~2020-12-04 17:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 20:15 Designing people and organization management for Emacs Jean Louis
2020-12-04 9:56 ` Eric S Fraga
2020-12-04 13:12 ` Pankaj Jangid
2020-12-04 13:38 ` Jean Louis
2020-12-04 14:52 ` Christopher Dimech
2020-12-04 15:21 ` Jean Louis
2020-12-04 16:09 ` Christopher Dimech
2020-12-04 16:20 ` Eric S Fraga
2020-12-05 3:14 ` Pankaj Jangid
2020-12-06 15:41 ` Eric S Fraga
2020-12-04 16:26 ` Jean Louis
2020-12-04 16:42 ` Christopher Dimech
2020-12-04 17:56 ` Jean Louis [this message]
2020-12-04 18:05 ` Christopher Dimech
2020-12-04 18:23 ` Jean Louis
2020-12-04 19:43 ` Christopher Dimech
2020-12-04 21:21 ` Jean Louis
2020-12-05 6:11 ` 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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X8p4NOPHv3Zb8HAe@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).