-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
name_number - set MANDATORY? #3
Comments
@sjib to do write concept for this as discussed |
|
I saw that we also do not have MANDATORY constraints in the postgres data model of tww - discuss with Technical group |
@urskaufmann How and where did we add this in tww? In the project file or as trigger in the database? |
Name_Nummer (=Identifier) is in tww normally not defined in the project. There must be somewhere a trigger, that sets identifier = obj_id as default value. With one exception: all identifier (reach, channel, reachpoint) in vw_tww_reach do not work like this, there has to be the obj_id defined as default value. The vw_tww_reach is somewhere specially, it's to only view, where the QGIS-standard-"reuse last value" does not work... |
These triggers seem to be created here in tww: In the final database it then looks like this:
|
@urskaufmann In vw_tww_reach there is nothing defined for NEW wwn.identifier - may be that is the reason: |
Name_Nummer (name_number) – in INTERLIS not MANDATORY – how to handle in TEKSI Distance heating?
I would suggest to set it MANDATORY
The text was updated successfully, but these errors were encountered: