Opened 9 years ago
Closed 9 years ago
#3120 closed enhancement (fixed)
Improve upgrade tester by adding some postgis objects before upgrade
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 2.2.0 |
| Component: | build | Version: | master |
| Keywords: | Cc: |
Description
For better upgrade testing it's worth creating some objects before the upgrade. That's how #3118 could have be cough earlier. I've a patch ready here: http://strk.keybit.net/tmp/extended_upgrade_test.patch
This ticket is to discuss it if needed.
One critical thing, for example, is to make sure the objects construction does not use functions which were not available at the time of the initial installation (think —upgrade-path).
Maybe a better approach could be to let the caller specify a filename containing the upgrade preparation and another containing the upgrade cleanup scripts. And to allow for these filenames to be dependent on the source version.
Note:
See TracTickets
for help on using tickets.
r13518 in trunk. For core, only creates a table with a geometry and a geography fields (no AddGeometryColumns, no constraints). For raster, it adds a raster column to the table and add constraints (no parameters to the function). For topology it creates a topology (no parameters to CreateTopology).
Enhancements can use other tickets.