Hibernate Spatial Dialects: Integrate into parent (non spatial) Dialect classes

Description

Before the integration of the separate project "Hibernate Spatial" into the "Hibernate ORM" project, it was ok that there exist extra classes for the spatial dialects (project "Hibernate Spatial") which are derived from the standard dialect classes (project "Hibernate ORM").

But now (the spatial dialects are part of the "Hibernate ORM" project), this is not necessary any longer.

I have got this problem: There is a SqlServer2008SpatialDialect which is derived from SQLServer2008Dialect. And there is a SQLServer2012Dialect which is derived from SQLServer2008Dialect, too. But there is no SqlServer2012SpatialDialect (spatial dialect which is derived from SQLServer2012Dialect) .

The same problem exists for Oracle: There is a OracleSpatial10gDialect which is derived from Oracle10gDialect. And there is a Oracle12cDialect which is derived from Oracle10gDialect, too. But there is no OracleSpatial12cDialect (spatial dialect which is derived from Oracle12cDialect).

The same problem may exist for all other spatial dialects.

If you integrate the features from SqlServer2008SpatialDialect into SQLServer2008Dialect (and drop the SqlServer2008SpatialDialect, or keep it as empty implementation), then the SQLServer2012Dialect would automatically have the spatial features.

If you integrate the features from OracleSpatial10gDialect into Oracle10gDialect (and drop the OracleSpatial10gDialect, or keep it as empty implementation), then the Oracle12cDialect would automatically have the spatial features.

The same solution would work for all other spatial dialects.

Environment

None

Status

Assignee

Unassigned

Reporter

Alfred Staflinger

Fix versions

None

Labels

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Priority

Major