unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim Landscheidt <tim@tim-landscheidt.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Interacting with PostgreSQL
Date: Wed, 25 Nov 2020 17:08:18 +0000	[thread overview]
Message-ID: <87sg8xtldp.fsf@passepartout.tim-landscheidt.de> (raw)
In-Reply-To: X75pdIYyxtOKWK1U@protected.rcdrun.com

Jean Louis <bugs@gnu.support> wrote:

>> The problem is that you do not need to consciously use auto-
>> commit mode, but that psql automatically reverts to it when
>> you rollback or commit a transaction:

>> | tim=> BEGIN WORK;
>> | BEGIN
>> | tim=> INSERT INTO t (ID) VALUES (1);
>> | INSERT 0 1
>> | tim=> ROLLBACK WORK;
>> | ROLLBACK
>> | tim=> INSERT INTO t (ID) VALUES (1);
>> | INSERT 0 1
>> | tim=> -- The row has been committed.

> I understand. I always used it manually and will rather continue. Just
> observing how you do it.

Eh, that /is/ the behaviour using it manually, either on the
command line or via sql-postgres.

> […]

> Do you use any kind of revision system?

> I have made recently my own revision system, you can see the simple
> table below, and `hyperscope-vc' that fetches values and inserts into
> the "version control" table.

> […]

> If you know other ways of version control, let me know.

> […]

If I were to choose a system for storing structured informa-
tion, I would almost certainly not use a system that accord-
ing to https://github.com/BradNeuberg/hyperscope (last up-
dated six years ago) "is not currently maintained.  It is
present here for archival purposes."

There are org-mode, many markdown variants, plain HTML, and
apparently even a dedicated GNU project called Hyperbole
(https://www.gnu.org/software/hyperbole/).  There are a my-
riad of version control systems, with Git at the forefront.
Most of them are natively supported by Emacs, right out of
the box.

I find that there is a lot of strength in numbers and thus
I like to use software that is used by at least a sizable,
critical mass of other users.  This gives me confidence that
if I encounter a problem, either a bug or just a question of
how to achieve something in the most effective or efficient
way, others will have treaded that path before me and
hopefully left some breadcrumbs.  And if I am genuinely the
first one to tackle an issue, my solution to it will not
only benefit myself, but also others who may face the same
questions.

Tim




  reply	other threads:[~2020-11-25 17:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21 23:51 Interacting with PostgreSQL Tim Landscheidt
2020-11-22  1:33 ` Jean Louis
2020-11-24 23:14   ` Tim Landscheidt
2020-11-25  4:18     ` Jean Louis
2020-11-25 10:37       ` Tim Landscheidt
2020-11-25 14:25         ` Jean Louis
2020-11-25 17:08           ` Tim Landscheidt [this message]
2020-11-27  1:40             ` Jean Louis
2020-11-30  3:12               ` Tim Landscheidt
2020-11-30  9:12                 ` Jean Louis
2020-11-22 21:33 ` Marcin Borkowski
2020-11-24 20:42   ` Tim Landscheidt
2020-11-27  2:01   ` 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=87sg8xtldp.fsf@passepartout.tim-landscheidt.de \
    --to=tim@tim-landscheidt.de \
    --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).