Re: libpq URL syntax vs SQLAlchemy

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: libpq URL syntax vs SQLAlchemy
Дата
Msg-id CA+U5nMLjMu7XrG__-=03BWvrOZqR-Z=Y0K84ei2TNMi5eNPCGg@mail.gmail.com
обсуждение исходный текст
Ответ на libpq URL syntax vs SQLAlchemy  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: libpq URL syntax vs SQLAlchemy  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-hackers
On 9 May 2012 19:17, Peter Eisentraut <peter_e@gmx.net> wrote:

> I have been reviewing how our new libpq URL syntax compares against
> existing implementations of URL syntaxes in other drivers or
> higher-level access libraries.  In the case of SQLAlchemy, there is an
> incompatibility regarding how Unix-domain sockets are specified.

Is there an open standard that already defines this? If there is an
existing standard we should follow it, so we can quote "we now follow
standard X".

If there isn't one, can we create one? Can we propose an RFC that
works for many data stores?

If somebody can define that, I can push that through the relevant
processes. Not because I wish PostgreSQL syntax to be badged as a
standard, but because the world clearly needs a useful, open standard
here.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: PL/Python result set slicing broken in Python 3
Следующее
От: Simon Riggs
Дата:
Сообщение: External Open Standards