Comments (8)
would this be an option in the relation?
from qgep.
Yes, I think this should be an option in the relation.
We could think of making fields joined in such a way easily accessible (if it's a parent object, it's attributes can be thought of almost like real properties of the child object)
from qgep.
but there still should be a check because there is no mean to know for sure that there is striclty 1 joined feature. There should be a warning if 0 or 2+ joined features are found.
from qgep.
If there is demand for this, then we should add it as an option or as an on-demand check.
This check is possibly expensive and I don't think it is QGIS' job to guarantee this, I'd rather see that on database side.
from qgep.
I agree with Matthias. The application designer needs to make sure that 1:1 relations are really 1:1 or 1:0.
Andreas
from qgep.
Synchronizing the editable state of the two layers may be desirable as well.
I am thinking of a click less (pencil) when editing attributes that belong to structure part when on the cover form. How should propagation be handled (there are other tables with structure parts like access aid, should it be always either all structure part tables or none?)
from qgep.
I think the QGEP plugin should provide a way to set all relevant relations to editable at once. Depending on the edit task this would mean different relations. Something to find out during the prototyping phase.
from qgep.
Closed in favor of #55
from qgep.
Related Issues (20)
- Wizard new reach Error creating new reach without rp_levels HOT 13
- Label not showing a newly connected reach. HOT 1
- Postgis 3.3 needs QGEP datamodel adaptations to work
- TX : Translation of some but not all value_en to value_xx HOT 2
- Bring colors and style to forms
- Postgres 15 needs QGEP datamodel adaptations to work HOT 3
- Handling of "clear_width" HOT 3
- Timing of "Apply default value on update" HOT 2
- Interlisexport: TextVAli is Bottom, not Top HOT 3
- GitHub 2FA fails and you might loose all access to account and projects here. HOT 5
- Fieldcalculator on gpkg-field blocks qgep-project HOT 2
- vl_ values are not prefixed as such in database but still referenced as vl_ values in the project HOT 2
- Performance on QGEP is not monitored and scalability is not accessed HOT 1
- SWMM export of selected features only works in english
- Gestion des droits Postgres HOT 3
- Missing dependency sqlalchemy HOT 1
- Error whem deleting special structure HOT 2
- Lost relations in copy of the project HOT 2
- INTERLIS export fails using latest plugin HOT 8
- Testing qgep plugin 1.6.2 - Project file missing layers HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from qgep.