| [geogig-dev] Some questions about data modeling |
|
Hi all, we have a data model modelled in PostGIS containing
·
some Foreign Key Constraints,
·
Some Unique Constraints ·
Some compound Keys (for M:N Join relationship tables) ·
Some specialized Indices for fast data access Now my question is if there are ways to keep those elements inside a geogig repository? Or do I need to maintain those objects in a different way outside geogig? When doing a pg import I’m able to specify which row is the primary key for a feature – is there a way to deal with a compound key? My use case is the following: I have a table builidings and a table addresses, which can be m:n joined with a relationship table. It’s primary key is compound of (building_id, address_id) in order to disallow
multiple relations. How could I preserve that behavior from pg import -> geogig -> pg export into a fresh database/schema? Kind regards, Sebastian Mit freundlichen Grüßen Sebastian Schmidt S-IP-AN-TG Techn. Geschäftsfelder |