Using Monitoring into an Oracle DB fails due to use of reserved word RESOURCE
as a column name
----------------------------------------------------------------------------------------------
Key: GEOS-4871
URL: https://jira.codehaus.org/browse/GEOS-4871
Project: GeoServer
Issue Type: Bug
Components: Community modules
Affects Versions: 2.1.2
Environment: Monitoring DB - Oracle
Reporter: Martin Davis
Assignee: Andrea Aime
Monitoring creates a table
REQUEST_RESOURCES
(REQUEST_ID number(19,0) not null, RESOURCE varchar2(255 char), IDX
number(10,0) not null, primary key (REQUEST_ID, IDX))
RESOURCE is a reserved word in Oracle SQL, so using Monitoring into an Oracle
DB fails during schema creation.
The fix is to change the column name - Justin suggests NAME.
Upgrade of existing installs may be able to be done automatically via Hibernate
"hibernate.hbm2ddl.auto" configuration option. Otherwise, users should be
informed to manually alter the table when upgrading.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
