Bug report #18289

GIS 3 Atlas not work with oracle spatial layer

Added by dany Lefeuvre over 6 years ago. Updated over 6 years ago.

Status:Closed
Priority:High
Assignee:-
Category:Map Composer/Printing
Affected QGIS version:3.0.0 Regression?:Yes
Operating System:Windows 7 professionnal Easy fix?:No
Pull Request or Patch supplied:No Resolution:fixed/implemented
Crashes QGIS or corrupts data:No Copied to github as #:26180

Description

When my atlas is created on an oracle spatial layer, it can't locate itself on feature.
When I try with a spatialite layer atlas is ok.

Associated revisions

Revision 7ffc148e
Added by Nyall Dawson over 6 years ago

[oracle] Fix provider

The oracle provider is quite broken on 3.0 for tables which require
a feature id map.

This is due to QMap<QVariant,..> not working correctly when the
keys are QVariantLists on Qt5. We had a similar issue with the
postgres provider which was resolved by changing the map
to always use QVariantLists.

Apply the same fix to oracle.

Fixes #18289, #16869, #17738

Revision 5234212e
Added by Nyall Dawson over 6 years ago

[oracle] Fix provider

The oracle provider is quite broken on 3.0 for tables which require
a feature id map.

This is due to QMap<QVariant,..> not working correctly when the
keys are QVariantLists on Qt5. We had a similar issue with the
postgres provider which was resolved by changing the map
to always use QVariantLists.

Apply the same fix to oracle.

Fixes #18289, #16869, #17738

(cherry-picked from 7ffc148)

History

#1 Updated by Giovanni Manghi over 6 years ago

  • Status changed from Open to Feedback

It works ok with 2.18?

#2 Updated by dany Lefeuvre over 6 years ago

Yes, there are no problem on 2.18

#3 Updated by Giovanni Manghi over 6 years ago

  • Status changed from Feedback to Open

#4 Updated by Nyall Dawson over 6 years ago

  • % Done changed from 0 to 100
  • Status changed from Open to Closed

#5 Updated by Giovanni Manghi over 6 years ago

  • Resolution set to fixed/implemented

Also available in: Atom PDF