[postgis-devel] Extension Versions

[Paragon Corporation]

 One more note -- which would make strk happy -- there is a provision for
custom tables to mark records as custom or not.

Form that link - the example

CREATE TABLE my_config (key text, value text, standard_entry boolean);

SELECT pg_catalog.pg_extension_config_dump('my_config', 'WHERE NOT
standard_entry');

> -----Original Message-----
> From: Paragon Corporation [mailto:lr at pcorp.us] 
> Sent: Monday, January 09, 2012 6:09 PM
> To: 'Paul Ramsey'
> Cc: 'postgis-devel at postgis.refractions.net'
> Subject: RE: Extension Versions
> 
>  
> While we are on the topic of extensions,  there is one thing 
> I did not do that I was meaning to do and shoudl be done 
> before release.
> 
> That is to mark the spatial_ref_sys, and the various topology 
> tables as editable.
> 
> Now that raster and geometry tables are views -- thank 
> goodness, 3 less things to make editable.
> 
> I think that has to be done in one of the .sql files, but I 
> forget the exact syntax. 
> Somehwere on this page as I recall:
> 
> http://www.postgresql.org/docs/9.1/static/extend-extensions.html
> 
> 
> It is short and sweet but will be different for topology and postgis.
> 
> When you mark a table as editable, the data is backed up when 
> a user backs up their data, but the structure of the table 
> comes from the extension definition so is not stored with the 
> database backup.
> 
> Thanks,
> Regina
>