Skip to content

Releases: QGEP/datamodel

1.0.1-4

22 May 14:05
Compare
Choose a tag to compare
try with dump rather than plain SQL for data only

1.0.1-3

22 May 13:46
Compare
Choose a tag to compare
fix demo dump

fix baseline

21 May 18:43
Compare
Choose a tag to compare
1.0.1-2

fix read again

1.0.1: add prefix in views (#68)

25 Apr 19:01
41ab5fb
Compare
Choose a tag to compare

Prefixes

This release changes the 2 main views of QGEP (wastewater structures and reaches) by adding prefixes to field names.
This work has been done in #68 and #53

View for files

This release also brings a new view for files.
See #66

1.0

18 Apr 18:05
Compare
Choose a tag to compare

We are proud to announce QGEP 1.0 release!

What's new ?

Datamodel upgrade system

PUM aka the Postgres Upgrade Manager has been integrated into QGEP datamodel. PUM is also available as PyPi package (pip install pum).
This means that every addition to the data model must be accompanied by a delta file which will be applied on production environment to upgrade the model to the latest release. This delta file is controlled to guarantee that applying it to a former model version leads to the exact same structure like a fresh install.

Schema dispatch

Former version contained a single qgep schema. The new version dispatches the table into 3 schemas (qgep_od for ordinary tables, qgep_vl for value lists and qgep_sys for system administration tables).

Roles and rights

Thanks to the schema dispatch, QGEP 1.0 allows a finer tuning of access rights to the data model with 4 levels:

  • viewer: view all tables
  • user: viewer + write access to qgep_od
  • manager: user + write access to qgep_vl
  • sys admin: manager + write access to qgep_sys

How do I upgrade ?

If you are already in production on a former model, we provide a script to upgrade to 1.0.0. The procedure to perform this upgrade can be found here.

Next model updates will be as simple as running a one line command using pum test-and-upgrade (and a few arguments).

Do not hesitate to contact us if you need assistance for upgrading.

20180414-160538: update test/demodata (#65)

14 Apr 16:05
6899408
Compare
Choose a tag to compare
* update test/demodata

* fix version number

* use pg_dump 9.6 to produce a proper version

* try to upgrade postgresql

* run as sudo

* update client only

* try with postgis 2.4

* take 2 at postgis 2.4

* upgrade client again

* remove older pg versions

* fix role in dump

* fix owner take 2

* complete dump

* demodata restored on freshly created db

* add submodule with demodata

* remove bad submodule folder

* fix submodule

* do not check public schema in pum

* avoid restoring public schema

* fix var in string

* avoid drop/recreating roles

* remove public schema (postgis) from demo data

* fix pum new arguments

* remove demodata submodule

* add deploy script

20180212-171410: Merge pull request #64 from elemoine/ele_fix-migration

12 Feb 17:14
d199cda
Compare
Choose a tag to compare

20180202-153911: Merge pull request #60 from marioba/master

02 Feb 15:39
f2bb89c
Compare
Choose a tag to compare

20180202-152934: Merge pull request #62 from QGEP/optional_roles

02 Feb 15:29
611c762
Compare
Choose a tag to compare

20180202-144453

02 Feb 14:44
ff3bb2d
Compare
Choose a tag to compare
fix schema name typo