-
Notifications
You must be signed in to change notification settings - Fork 29
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
Handle setting geometry column name for GDAL 3.6+ #123
Conversation
Pull Request Test Coverage Report for Build 8388745198Details
💛 - Coveralls |
61859f8
to
79cc9be
Compare
godal.go
Outdated
@@ -2861,6 +2861,7 @@ func (f *Feature) SetGeometry(geom *Geometry, opts ...SetGeometryOption) error { | |||
return cgc.close() | |||
} | |||
|
|||
// Deprecated: when running with GDAL 3.6+, you may use SetGeometryColumnName on Layer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking we should change this method's signature to return an error, and explicitely return a go error without going into cgo/gdal for version>=3.6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or for version>3.9 actually no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comments and method signature changed. Tell me if it's ok so I squash commits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we look at the coverage, I wonder if we may create a cpp function so we check version in cpp code, like for other functions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As you prefer. I am not very concerned by the coverage percent for this particular issue. If you were to move it all to cpp (which is effectively cleaner and a bit more in line with what we do elsewhere in godal), your coverage would still not be ideal as it would not be possible to write a test handling both the error and no-error cases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New changes done. When moving to cpp, as errors are handled in a proper way, we don't even need to check version.
2c3d0da
to
810c0d9
Compare
LGTM |
810c0d9
to
f3468c3
Compare
No description provided.