Changes between Version 12 and Version 13 of PostGISExtensionPaths

Timestamp:

02/11/22 11:21:20 (3 years ago)

Author:

robe

Comment:

--

PostGISExtensionPaths

@@ -87 +87 @@
 In this model, our extension files look like below:
 
-our generated extension upgrade scripts will look like the below, with only the postgis--3.3MAX--3.3.0.sql having any upgrade statements in it.
+our generated extension upgrade scripts will look like the below, with only the postgis--3.3.X--3.3.0.sql having any upgrade statements in it.
 
 ----
@@ -100 +100 @@
 postgis--3.2.X--3.3.X.sql
 postgis--3.3.X--3.3.0.sql
+postgis--3.3.0--3.3.X.sql
 }}}
 ----
@@ -105 +106 @@
 
 1. We are staying between the lines. Respecting known practices, but still having much lighter weight scripts.
-2. A little less clutter, but we are relying on the user having the old version still installed so that they have a chain 
-postgis--<old-version-minor>MIN--<old-version-minor>MIN.sql
+2. A little less clutter, but we are relying on the user having the old version still installed (or being within 2 micro versions of the last minor they have installed) so that they have a chain 
+postgis--<old-version-minor>.X--<old-version-minor-verson>.sql
 3. An easier release cycle since extensions/updateable.mk doesn't need to list the prior micros.
 4. No change in upgrade extension workflow for packagers (or users who think of PostGIS as any other extension).