Bug report #10374

moving object function disabled with Oracle provider

Added by sylvain pierre over 6 years ago. Updated over 2 years ago.

Status:Closed
Priority:Normal
Assignee:-
Category:Data Provider/Oracle
Affected QGIS version:2.2.0 Regression?:No
Operating System:windows Easy fix?:No
Pull Request or Patch supplied:No Resolution:invalid
Crashes QGIS or corrupts data:No Copied to github as #:18793

Description

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

History

#1 Updated by Jürgen Fischer over 6 years ago

  • Target version changed from Version 2.2 to Future Release - Lower Priority

#2 Updated by Jürgen Fischer over 6 years ago

  • Category changed from Data Provider to Data Provider/Oracle

#3 Updated by Jürgen Fischer over 6 years ago

  • Assignee set to Jürgen Fischer

#4 Updated by Jürgen Fischer over 6 years ago

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]

#5 Updated by sylvain pierre over 6 years ago

With french translation, properties are:
"Ajouter des entités, Supprimer des entités, Changer des valeurs attributaires, Créer un index spatial, Accès rapide aux entités via l'ID" =>
Add entity,delete entity, change attribute values, create spatial index, fast access via ID but no "Change geomatries".
I've looked for privilege fot the table I'm working on with my account and here is DELETE, INSERT, SELECT and UPDATE...

#6 Updated by sylvain pierre over 6 years ago

Another clue:
I think issue relies on QgsVectorDataProvider::ChangeGeometries property (I'm not a C++ expert;-))
This property value is set by scanning all_col_privs oracle view which in my case is totaly empty.
So I think it is a DBA problem.
My DBA has not implemented column level security.

#7 Updated by Jürgen Fischer over 6 years ago

sylvain pierre wrote:

This property value is set by scanning all_col_privs oracle view which in my case is totaly empty.

Correct.

So I think it is a DBA problem.
My DBA has not implemented column level security.

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.

#8 Updated by Giovanni Manghi over 3 years ago

  • Regression? set to No
  • Easy fix? set to No

#9 Updated by Jürgen Fischer about 3 years ago

  • Assignee deleted (Jürgen Fischer)

#10 Updated by Nyall Dawson over 2 years ago

  • Resolution set to invalid
  • Description updated (diff)
  • Status changed from Open to Closed

Appears not to be a qgis issue

Also available in: Atom PDF