GNU bug report logs - #40564
28.0.50; sql.el should add support PostgreSQL alias "postgresql" of "postgres"

Previous Next

Full log

View this message in rfc822 format

From: stardiviner <numbchild <at> gmail.com>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: "numbchild <at> gmail.com" <numbchild <at> gmail.com>, Michael Mauger <michael <at> mauger.com>, Michael Mauger <mmauger <at> protonmail.com>, "40564 <at> debbugs.gnu.org" <40564 <at> debbugs.gnu.org>
Subject: bug#40564: 28.0.50; sql.el should add support PostgreSQL alias "postgresql" of "postgres"
Date: Mon, 27 Apr 2020 13:08:08 +0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Stefan Kangas <stefan <at> marxist.se> writes:

> Michael Mauger <mmauger <at> protonmail.com> writes:
>
>> * Based on my understanding of this issue, I believe that this not a feature appropriate
>>   for sql-mode, but rather it represents a weakness in the EJC->SQL mapping. Sql.el has
>>   used `postgres' as the identifier of the PostgreSQL since the first commit in '99. It
>>   was exposed as a user visible variable in `sql-product-alist' in 2003. EJC is using a
>>   heuristic that may work for other products, but it definitely won't work for all (It is
>>   broken for EJC's `sqlserver', which is `ms' in sql.el).

Though I can accept first copy identify to add a new one identity "postgresql" as solution.

Actually, not just in package ejc-sql has this identify problem, in Org Mode's
ob-sql.el also has this problem. And I think "postgres" is an historical name.
(Maybe I misunderstand it https://en.wikipedia.org/wiki/PostgreSQL)

Here is a related discussion thread archive
(https://lists.gnu.org/archive/html/emacs-orgmode/2020-01/msg00347.html).

This two extensions are used by me. Maybe there are other extensions.

Anyway, I can accept maintainer's solution, in private email communication, I
have already accepted, just I also send email here at that time. So I express my
thought.

>
> Thanks.  If I understand correctly, the recommendation is to report
> this to the ejc developers.
>
> Does that mean that this bug should be closed as "wontfix"?  Or is
> there anything more to do here?
>
> Best regards,
> Stefan Kangas

-----BEGIN PGP SIGNATURE-----

iQFIBAEBCAAyFiEE8J9lDX1nSBmJJZFAG13xyVromsMFAl6maLgUHG51bWJjaGls
ZEBnbWFpbC5jb20ACgkQG13xyVromsPiyggAz0upYIt9FEE53hPcNiQe3aZgshOI
qDZn87Gp8v3g6dqIfcmPYy1z2LgOwwm2IDwk+4VDuWXO1H28axEqw/PDoFfVKGgq
ZiOCQc0RGgKL1rBw6c3QlHHQvpt//ZpgfhbHK9pQVuJV68dUt/0kftEmvCmDBCPf
fqwnxPSbXQEo8xaplrGDx3NsRGSz+LTHxZt/oH71TcvPtSBFD2KHO8QtDmGvyQUB
cJCtF75r1NuHILwYUCVSPe8v2CAFrMTFNPzXD/JB6FDf7cAaOkuxQP4VeMARHQ7h
RAQwwz9Hdhu8A1d0ev9yl7/TAIJcpbVYhPhNdR6yuup9+LJpR1vNBOLJzQ==
=d+3/
-----END PGP SIGNATURE-----

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.