You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that one of the first step should be to agree on the way we use the db. I will try to resume the ones we discussed and write down pros and cons.
We use editing mode as it is right now.
keep usual way of editing
we cannot use object that are not in the db yet, and therefore we cannot create objects in a chain
We save the element in the db as soon as they are created
can create objects in chain
not usual way of editing in qgis
no undo redo
We create the uuid in qgis
we can create objects in chain
we can use undo redo
we keep editing mode style, i.e. start and stop editing
We use negative ids of qgis
the same as for choice 3
we need to create rules for insertion by using the correct ids and doing the insertion in a special order to avoid the break of foreign keys.
In all of the four cases, it should not be a problem to use something else than Postgres. It might be useful for a small town with a single user to use qgis with SQLite, as there is no special setup...
The text was updated successfully, but these errors were encountered:
I think that one of the first step should be to agree on the way we use the db. I will try to resume the ones we discussed and write down pros and cons.
In all of the four cases, it should not be a problem to use something else than Postgres. It might be useful for a small town with a single user to use qgis with SQLite, as there is no special setup...
The text was updated successfully, but these errors were encountered: