Re: Add CREATE EXTENSION Support

Поиск
Список
Период
Сортировка
От David E. Wheeler
Тема Re: Add CREATE EXTENSION Support
Дата
Msg-id 27035715-8D1E-4CED-981F-B35C5926B831@justatheory.com
обсуждение исходный текст
Ответ на Re: Add CREATE EXTENSION Support  (Dave Page <dpage@pgadmin.org>)
Ответы Re: Add CREATE EXTENSION Support  (Dave Page <dpage@pgadmin.org>)
Список pgadmin-hackers
On Feb 12, 2014, at 2:21 AM, Dave Page <dpage@pgadmin.org> wrote:

> Much as PostgreSQL only changes catalogs and on disk format in major
> releases, pgAgent only changes its schema in X releases (in the X.Y.Z
> numbering scheme). My point is that there is no need to have upgrade
> scripts from 3.3.0 - 3.4.0 or even 3.3 - 3.4 because there will never
> be any such changes, and using that numbering is likely to confuse
> users because the existence of a 3.4.0 script implies that there also
> should be one for 3.4.1 or 3.5.0 in the future, when in actual fact,
> there will only be one needed for 4(.x.x).
>
> Therefore, I believe the correct option is actually to have
> "pgagent--unpackaged--3.sql" and later "pgagent--3--4.sql" for
> upgrades.

Yeah, but if the version is 3.4.0, and that's what's in pgagent.spec, then Postgres will never find the upgrade script
ifit’s not named "pgagent--unpackaged--3.4.0.sql". The name in the file must be the same as in the spec file. 

Best,

David



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

Предыдущее
От: Dave Page
Дата:
Сообщение: Re: Ways to improve PgAdmin III SQL context help
Следующее
От: Guillaume Lelarge
Дата:
Сообщение: pgAdmin III commit: Give more options with the plain format