Skip to content
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

Oracle provider: fix compiler warnings #33930

Merged
merged 1 commit into from
Jan 21, 2020

Conversation

rouault
Copy link
Contributor

@rouault rouault commented Jan 20, 2020

  • Remove use of surfaceType variable that is never read
  • Avoid self assignment of nRings variable

- Remove use of surfaceType variable that is never read
- Avoid self assignment of nRings variable
@nyalldawson nyalldawson merged commit f84d90d into qgis:master Jan 21, 2020
@nyalldawson
Copy link
Collaborator

Unrelated test failure (@manisandro you merged a PR which was reporting a build failure on the Windows azure builds -- fix inbound)

rouault added a commit to rouault/QGIS that referenced this pull request Jan 21, 2020
When fixing warnings of qgis#33930, I
looked at the code that transforms a QGIS geometry of type MultiSurface
to a Oracle geometry, and it appeared quite convoluted/risky (variables
being reaffected with values of other variables), and not
being able to deal with straight Polygon in MultiSurface.
The reverse situation (Oracle MultiSurface to QGIS MultiSurface) had the
same issue as well.

The MultiCurve/CompoundCurve code has been modified similarly. There was
no real bug. Just a sub-optimal behaviour on reading of MultiCurve
from Oracle, where all parts where promoted to CompoundCurve, even when
not strictly needed.
@manisandro
Copy link
Member

@nyalldawson Sorry about that and thanks for fixing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants