Ticket #729 (closed defect: fixed)

Opened 4 months ago

Last modified 4 months ago

Hardcoded type name and attributes in spatial index feature for Oracle thru JNDI don't work

Reported by: simonp Owned by: jesseeichar
Priority: major Milestone: v2.7.0
Component: General Version:
Keywords: Cc:

Description

Attempting to use spatialindex in database for Oracle thru JNDI in GeoNetwork 2.7 - doesn't work because typenames and attributes (coded as static strings in Java) are not in uppercase.

Better to look (ignoring case) for typename and attributes in the datastore and use what we find there instead rather than hardcode one way of doing this.

Patch to appear shortly.

Change History

Changed 4 months ago by simonp

  • owner changed from geonetwork-devel@… to simonp

Changed 4 months ago by jesseeichar

  • owner changed from simonp to jesseeichar

Changed 4 months ago by jesseeichar

  • status changed from new to closed
  • resolution set to fixed

Commit 8563 has a fix for this issue. I would appreciate a review and comments

Changed 4 months ago by simonp

Reviewed 17/01/11 using Oracle spatial thru JNDI - works nicely Also checked the usual suspects - works fine there too. Thanks Jeese.

Note: See TracTickets for help on using tickets.