-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
moving object function disabled with Oracle provider #18793
Comments
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jürgen Fischer (@jef-n) Does "Editing capabilities of this layer" in the meta data page of the layer's properties include "Change Geometries"? It should, if you have UPDATE privilege on the geometry column of the table in Oracle. [BTW your email address bounces] |
Author Name: sylvain pierre (sylvain pierre) With french translation, properties are: |
Author Name: sylvain pierre (sylvain pierre) Another clue: |
Author Name: Jürgen Fischer (@jef-n) sylvain pierre wrote:
Correct.
I didn't know that you can disable it - and I can't find any pointer how or how you can verify whether it's enabled or not. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Nyall Dawson (@nyalldawson) Appears not to be a qgis issue
When I try to edit point layer, moving object function is disabled. With postgis layer, function is enabled. Regards Sylvain to QGIS 2.2 with connection to Oracle spatial. When I try to edit point layer, moving object function is disabled. With postgis layer, function is enabled. Regards Sylvain
|
Author Name: sylvain pierre (sylvain pierre)
Original Redmine Issue: 10374
Affected QGIS version: 2.2.0
Redmine category:data_provider/oracle
QGIS 2.2 with connection to Oracle spatial.
When I try to edit point layer, moving object function is disabled.
Adding function is enabled an run well.
With postgis layer, function is enabled.
Regards
Sylvain
The text was updated successfully, but these errors were encountered: