From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: Toggle appointment notification Date: Fri, 4 Dec 2020 10:11:26 +0300 Message-ID: References: <875z5ibigp.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12242"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Cc: Michael Heerdegen , help-gnu-emacs@gnu.org To: pietru@caramail.com Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Fri Dec 04 08:16:01 2020 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kl5Jx-00034y-4C for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 04 Dec 2020 08:16:01 +0100 Original-Received: from localhost ([::1]:39312 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kl5Jv-0004wU-9O for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 04 Dec 2020 02:15:59 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42862) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kl5Il-0004w1-9I for help-gnu-emacs@gnu.org; Fri, 04 Dec 2020 02:14:47 -0500 Original-Received: from static.rcdrun.com ([95.85.24.50]:38923) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kl5If-0004aY-CY for help-gnu-emacs@gnu.org; Fri, 04 Dec 2020 02:14:46 -0500 Original-Received: from localhost ([::ffff:197.157.0.57]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002C0006.000000005FC9E1DE.00002721; Fri, 04 Dec 2020 07:14:38 +0000 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=95.85.24.50; envelope-from=bugs@gnu.support; helo=static.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:125961 Archived-At: > > There is nothing that I think of the database unless during the > > development stage. Once developed functions work for years, I just > > looked back and I see decades passed. I could as well stay working > > with the old PostgreSQL version. Inside of a database is text. All > > editing is text. > > Wouldn't you need some database model to build? Databases like SQL need always table design, and it is very simple to do: CREATE TABLE aliases ( aliases_id SERIAL NOT NULL PRIMARY KEY, aliases_alias TEXT, aliases_name TEXT, aliases_email TEXT ); that above is approach with unique ID that I always recommend or it may be simpler without it: CREATE TABLE aliases ( aliases_alias TEXT, aliases_name TEXT, aliases_email TEXT ); Then few functions to insert aliases provide reliable structure for email aliases that would last for decades. Above is very simple example. Emacs configuration could as well be stored in the database and one could cycle through whole complex configurations with one key only, edit such, export into init file and similar, share with others.