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

PGgeo-PGgeometry-PGgeography class hierarchy #80

Merged

Conversation

phillipross
Copy link
Contributor

#55

  • Renamed test in postgis-geometry test suite

  • Introduced new JDBC PGobject extensions class hierarchy which now allows jdbc queries to return geometry or geography data with specific types which callers can use to differentiate which data type was queried

  • Cleanup and better documentation for DriverWrapper

  • Renamed AutoRegistrationTest to DatatypesAutoRegistration to better reflect what is being tested

  • Added geography as one of the castTypes in the EmptyGeometriesTest class

  • Added instantiation test for PGgeography to DatatypesTest class

  • Added GeographyDatatypeTest to verify new PGgeo/PGgeometry/PGgeography class hierarchy

  • Added PGgeography to driverconfig.properties

postgis#55

- Renamed test in postgis-geometry test suite

- Introduced new JDBC PGobject extensions class hierarchy which now allows jdbc queries to return geometry or geography data with specific types which callers can use to differentiate which data type was queried

- Cleanup and better documentation for DriverWrapper

- Renamed AutoRegistrationTest to DatatypesAutoRegistration to better reflect what is being tested

- Added geography as one of the castTypes in the EmptyGeometriesTest class

- Added instantiation test for PGgeography to DatatypesTest class

- Added GeographyDatatypeTest to verify new PGgeo/PGgeometry/PGgeography class hierarchy

- Added PGgeography to driverconfig.properties
@phillipross phillipross merged commit a77061a into postgis:master Mar 29, 2020
@phillipross phillipross deleted the feature/postgis-jdbc-geography branch March 29, 2020 21:04

/** {@inheritDoc} */
@Override
public void addGeometries(final Connection conn) throws SQLException {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason that geography is mapped to PGgeometry instead of PGgeography in this method, unlike the other methods?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't immediately see a reason why. It looks like an oversight in the refactoring.
It also looks like the mappings might be missing a mapping for geography that is not qualified by a schema.

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.

2 participants