From: Jean Louis <bugs@gnu.support>
To: Christopher Dimech <dimech@gmx.com>
Cc: uzibalqa <uzibalqa@proton.me>,
Bruno Barbier <brubar.cs@gmail.com>,
uzibalqa via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Format of lists and alists required for displaying lists of tabulated data
Date: Mon, 19 Jun 2023 21:49:17 +0300 [thread overview]
Message-ID: <ZJCjLWXGpQm5w6bM@lco.syogm.com> (raw)
In-Reply-To: <trinity-2448c96d-4486-4960-8886-2f83ab2f6fc0-1687115761837@3c-app-mailcom-bs02>
* Christopher Dimech <dimech@gmx.com> [2023-06-18 22:16]:
> The functions could be difficult to use because of the many calls to your "rcd-" functions.
> Perhaps we can come up with something more adept to users to try. Using same idea of
> an ID followed by values.
Yes, good idea. But I did not find use of it for me. All my PostgreSQL database tables follow certain pattern as described by:
GeDaFe - PostgreSQL Generic Database Interface:
http://gedafe.github.io/doc/gedafe-sql.en.html
and should be compatible with the web interface as well in that
sense. I did not test it for years, since I switched to Emacs
interface.
They follow this pattern "mytable_" plus "_id", so there is always
"ID" which serves handy for tabulated-list-mode
-- ------------------------------------------
-- ------------ Table mytable
-- ------------------------------------------
DROP SEQUENCE mytable_id_seq;
CREATE TABLE mytable (
mytable_id SERIAL NOT NULL PRIMARY KEY,
mytable_uuid UUID NOT NULL DEFAULT gen_random_uuid() UNIQUE,
mytable_datecreated TIMESTAMP DEFAULT CURRENT_TIMESTAMP NOT NULL,
mytable_datemodified TIMESTAMP,
mytable_usercreated TEXT NOT NULL DEFAULT current_user,
mytable_usermodified TEXT NOT NULL DEFAULT current_user,
mytable_name TEXT,
mytable_title TEXT,
mytable_description TEXT,
mytable_ TEXT
);
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-06-19 18:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 21:08 Format of lists and alists required for displaying lists of tabulated data uzibalqa
2023-06-17 7:36 ` Bruno Barbier
2023-06-17 12:33 ` uzibalqa
2023-06-17 20:54 ` Tim Landscheidt
2023-06-18 10:36 ` uzibalqa
2023-06-18 11:29 ` Tim Landscheidt
2023-06-18 13:20 ` uzibalqa
2023-06-18 13:37 ` uzibalqa
2023-06-18 13:51 ` uzibalqa
2023-06-18 15:31 ` Jean Louis
2023-06-18 19:11 ` uzibalqa
2023-06-19 18:46 ` Jean Louis
2023-06-18 19:16 ` Christopher Dimech
2023-06-19 18:49 ` Jean Louis [this message]
2023-06-19 18:59 ` uzibalqa
2023-06-21 4:48 ` Jean Louis
2023-06-21 10:45 ` uzibalqa
2023-06-24 19:19 ` 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=ZJCjLWXGpQm5w6bM@lco.syogm.com \
--to=bugs@gnu.support \
--cc=brubar.cs@gmail.com \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=uzibalqa@proton.me \
/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).