As far as layer_epsg is concerned, I had written an SQL to solve that
problem, see
http://www.mapbender.org/index.php/Database_Changes_2.4.1#layer_epsg
Strange that it didn't make it in 2.4.1 already
Christoph
Samson, Marko schrieb:
Hi devs,
I try to create a new up-to-date database diagramm with dbdesigner4 at the
moment. In the process I realised, that the tables layer_style and layer_epsg
have no primary-key and have some double entries(dump from 2.4.2rc1 for
postgres-utf8).
Is there a reason for double entries and missing pks? (or did we forget the pks
for those tables, last time we had the discusson about pks?)
select fkey_layer_id, name, count(*) from layer_style group by fkey_layer_id, name
having count(*) >1
select fkey_layer_id, epsg, count(*) from layer_epsg group by fkey_layer_id, epsg
having count(*) >1
What about primary keys:
pk_layer_style (fkey_layer_id, name)
pk_layer_epsg (fkey_layer_id,epsg)
Btw.
Perhaps it would be possible to save this or another diagramm at the svn to
have an up-to-date diagramm at every time? But we should have an agreement for
a standard db-tool or a file-format. (dbdesigner can export to mdb-xml, sql and
his own xml-format)
What do you think?
Greetings,
Marko Samson
Marko Samson
Landesbetrieb Wald und Holz NRW
GIS-Anwendungsentwicklung
Referat I-5
Albrecht-Thaer-Straße 34
48147 Münster
Tel.: 0251/91797 - 169
Mail: [EMAIL PROTECTED]
_______________________________________________
Mapbender_dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapbender_dev
--
Baudson Christoph
http://www.wheregroup.com
_______________________________________________
Mapbender_dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapbender_dev
