Re: ALTER EXTENSION ... UPGRADE;
От | Dimitri Fontaine |
---|---|
Тема | Re: ALTER EXTENSION ... UPGRADE; |
Дата | |
Msg-id | 87bp4p90zb.fsf@hi-media-techno.com обсуждение исходный текст |
Ответ на | Re: ALTER EXTENSION ... UPGRADE; (Aidan Van Dyk <aidan@highrise.ca>) |
Ответы |
Re: ALTER EXTENSION ... UPGRADE;
|
Список | pgsql-hackers |
Aidan Van Dyk <aidan@highrise.ca> writes: > Mainly, because of the situation where I have may versions that can > all be upgraded from the same script. I'ld much rather distribution > just 3 scripts (install + 2 upgrades), and a control file with > something like this (pretend I'm on version 2.6) > upgragde-1.0 = $EXT-upgrade-1.sql [...] > upgrade-2.5 = $EXT-upgrade-2.sql Thanks for the example. > Again, I'ld love for the "version" to support some sort of prefix or > wildcard matching, so I could do: > upgrade-1.* = $EXT-upgrade-1.sql > upgrade-2.* = $EXT-upgrade-2.sql Problem is: what to do if a single upgrade matches more than one line? The only safe answer is to error out and refuse to upgrade but that ain't nice to the user. How much is that a problem here? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
В списке pgsql-hackers по дате отправления: