all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Jean Louis <bugs@gnu.support>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Designing people and organization management for Emacs
Date: Fri, 4 Dec 2020 19:05:59 +0100	[thread overview]
Message-ID: <trinity-48f509eb-ab03-4d05-8a65-b04f27bf062a-1607105159495@3c-app-mailcom-bs11> (raw)
In-Reply-To: <X8p4NOPHv3Zb8HAe@protected.rcdrun.com>

> Sent: Friday, December 04, 2020 at 6:56 PM
> 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
>
> * 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.

Would things be general enough with your plan?  For instance,
settings fields and naming them, on which the queries would run.

Can test it out and ask others using it for their work.  Have some contacts
at the Osservatorio Vesuviano, Naples (Italy).

> Some references:
>
> https://aiven.io/blog/an-introduction-to-postgresql
>
> https://www.postgresqltutorial.com/
>
>



  reply	other threads:[~2020-12-04 18:05 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
2020-12-04 18:05                 ` Christopher Dimech [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-48f509eb-ab03-4d05-8a65-b04f27bf062a-1607105159495@3c-app-mailcom-bs11 \
    --to=dimech@gmx.com \
    --cc=bugs@gnu.support \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.