Re: [Geoserver-users] App schema feature chaining issue

2010-11-03 Thread Ryan Zoerb
Thanks for the response Ben.  GWSI_LEVELS is a table.  Here is the output from 
DESCRIBE GWSI_LEVELS:

DESCRIBE GW_DATA_PORTAL.GWSI_LEVELS
NameNullType


 
--  
-
 
AGENCY_CD   NOT NULLVARCHAR2(5)
SITE_NO NOT NULLVARCHAR2(15)
DATES   DATE
VALUE   NUMBER
REMARK  VARCHAR2(5)
REMARK_DS   VARCHAR2(255)
SOURCE_CD   VARCHAR2(5)
METHOD_CD   VARCHAR2(5)
METHOD_DS   VARCHAR2(255)
QW_ACCURACY VARCHAR2(5)
QW_ACCURACY_NM  VARCHAR2(255)
HOSTNOT NULLVARCHAR2(30)
DBNUM   NOT NULLVARCHAR2(2)
DWH_INSERT  DATE
LEV_CN  VARCHAR2(8)
LEV_CR  DATE
LEV_MN  VARCHAR2(8)
LEV_MD  NOT NULLDATE
GW_LEV_PK   NOT NULLNUMBER
MP_LEV_VA   VARCHAR2(7)
SL_LEV_VA   VARCHAR2(8)
LEV_ENT_CD  VARCHAR2(1)
LEV_STATISTICS_CD   VARCHAR2(1)
LEV_STATISTICS_NM   VARCHAR2(255)
DATE_ACY_CD VARCHAR2(1)
SL_DATUM_CD VARCHAR2(10)
LEV_PARTY_TXVARCHAR2(6)
LEV_WEB_CD  VARCHAR2(1)
LEV_AGENCY_CD   VARCHAR2(5)
LEV_MPNT_SEQ_NU NUMBER
LEV_RMK_TX  VARCHAR2(256)
LEV_EQPID_TXVARCHAR2(20)
DWH_SITE_ID NOT NULLNUMBER
PARAMETER_CODE  CHAR(5)
SOURCE  VARCHAR2(10)
VALUE_ALL   NUMBER


Thanks,
Ryan

On Nov 2, 2010, at 8:20 PM, Ben Caradoc-Davies wrote:

 Ryan,
 
 I do not think this is an app-schema problem as it is the inner feature type 
 that is affected and this error will likely occur before any chaining takes 
 place. My guess is this is either a subtle bug in the geotools oracle 
 support, or an unintended interaction with your database configuration. I 
 cannot find any hardcoded identifier TIMES in the code base.
 
 (1) Is GWSI_LEVELS a table, view, or materialized view?
 
 (2) What is the output of DESCRIBE GWSI_LEVELS?
 
 Kind regards,
 Ben.
 
 
 On 03/11/10 05:46, Ryan Zoerb wrote:
 Hi everyone.  I'm trying to get application schema with feature chaining 
 working, but I'm running into an issue.  I've attached the two mapping files 
 I'm using.  WaterWell is the top level element, which can have several 
 nested logElement's.  I've been able to successfully get GeoServer to return 
 a correct response without feature chaining, but when I added the chaining, 
 I get this Oracle error: 'ORA-00904: TIMES: invalid identifier'.  Here's 
 the query that GeoServer is doing that returns the error:
 
 SELECT 
 GW_LEV_PK,AGENCY_CD,SITE_NO,DATES,VALUE,REMARK,REMARK_DS,SOURCE_CD,METHOD_CD,METHOD_DS,QW_ACCURACY,QW_ACCURACY_NM,HOST,DBNUM,DWH_INSERT,LEV_CN,LEV_CR,LEV_MN,LEV_MD,MP_LEV_VA,SL_LEV_VA,LEV_ENT_CD,LEV_STATISTICS_CD,LEV_STATISTICS_NM,DATE_ACY_CD,SL_DATUM_CD,LEV_PARTY_TX,LEV_WEB_CD,LEV_AGENCY_CD,LEV_MPNT_SEQ_NU,LEV_RMK_TX,LEV_EQPID_TX,DWH_SITE_ID,PARAMETER_CODE,SOURCE,VALUE_ALL,AGENCY_CD,SITE_NO,DATES,VALUE,STATUS_CD,STATUS_DS,SOURCE_CD,METHOD_CD,METHOD_DS,QW_ACCURACY,QW_ACCURACY_NM,HOST,DBNUM,DWH_INSERT,LEV_CN,LEV_CR,LEV_MN,LEV_MD,TIMES,MP_LEV_VA,SL_LEV_VA,LEV_ENT_CD,LEV_STATISTICS_CD,LEV_STATISTICS_NM,DATE_ACY_CD,SL_DATUM_CD,LEV_PARTY_TX,LEV_WEB_CD,LEV_AGENCY_CD,LEV_MPNT_SEQ_NU,LEV_RMK_TX,LEV_EQPID_TX,DWH_SITE_ID
  FROM GWSI_LEVELS WHERE SITE_NO = ?
 
 The problem is that the GWSI_LEVELS table doesn't have a column called 
 TIMES.  All of the other columns are correct (even though most of them are 
 in that list twice).  The pattern I see is that the primary key, GW_LEV_PK, 
 is first in the list, then all of the columns are listed in the same order 
 they are in the db (except for GW_LEV_PK).  Then, all the columns except the 
 last three are listed again, but 

Re: [Geoserver-users] App schema feature chaining issue

2010-11-03 Thread Rini Angreani

Hi Ryan,

What does your chaining attribute look like in the mapping file? 
When does the error occur, when you make a request, or during startup?
Can you also attach a stack trace? Maybe I can help.

Cheers
Rini


Ryan Zoerb wrote:
 
 Thanks for the response Ben.  GWSI_LEVELS is a table.  Here is the output
 from DESCRIBE GWSI_LEVELS:
 
 DESCRIBE GW_DATA_PORTAL.GWSI_LEVELS
 Name  NullType
   
   
  
 -- 
 -
  
 AGENCY_CD NOT NULLVARCHAR2(5)
 SITE_NO   NOT NULLVARCHAR2(15)
 DATES DATE
 VALUE NUMBER
 REMARKVARCHAR2(5)
 REMARK_DS VARCHAR2(255)
 SOURCE_CD VARCHAR2(5)
 METHOD_CD VARCHAR2(5)
 METHOD_DS VARCHAR2(255)
 QW_ACCURACY   VARCHAR2(5)
 QW_ACCURACY_NMVARCHAR2(255)
 HOST  NOT NULLVARCHAR2(30)
 DBNUM NOT NULLVARCHAR2(2)
 DWH_INSERTDATE
 LEV_CNVARCHAR2(8)
 LEV_CRDATE
 LEV_MNVARCHAR2(8)
 LEV_MDNOT NULLDATE
 GW_LEV_PK NOT NULLNUMBER
 MP_LEV_VA VARCHAR2(7)
 SL_LEV_VA VARCHAR2(8)
 LEV_ENT_CDVARCHAR2(1)
 LEV_STATISTICS_CD VARCHAR2(1)
 LEV_STATISTICS_NM VARCHAR2(255)
 DATE_ACY_CD   VARCHAR2(1)
 SL_DATUM_CD   VARCHAR2(10)
 LEV_PARTY_TX  VARCHAR2(6)
 LEV_WEB_CDVARCHAR2(1)
 LEV_AGENCY_CD VARCHAR2(5)
 LEV_MPNT_SEQ_NU   NUMBER
 LEV_RMK_TXVARCHAR2(256)
 LEV_EQPID_TX  VARCHAR2(20)
 DWH_SITE_ID   NOT NULLNUMBER
 PARAMETER_CODECHAR(5)
 SOURCEVARCHAR2(10)
 VALUE_ALL NUMBER
 
 
 Thanks,
 Ryan
 
 On Nov 2, 2010, at 8:20 PM, Ben Caradoc-Davies wrote:
 
 Ryan,
 
 I do not think this is an app-schema problem as it is the inner feature
 type that is affected and this error will likely occur before any
 chaining takes place. My guess is this is either a subtle bug in the
 geotools oracle support, or an unintended interaction with your database
 configuration. I cannot find any hardcoded identifier TIMES in the code
 base.
 
 (1) Is GWSI_LEVELS a table, view, or materialized view?
 
 (2) What is the output of DESCRIBE GWSI_LEVELS?
 
 Kind regards,
 Ben.
 
 
 On 03/11/10 05:46, Ryan Zoerb wrote:
 Hi everyone.  I'm trying to get application schema with feature chaining
 working, but I'm running into an issue.  I've attached the two mapping
 files I'm using.  WaterWell is the top level element, which can have
 several nested logElement's.  I've been able to successfully get
 GeoServer to return a correct response without feature chaining, but
 when I added the chaining, I get this Oracle error: 'ORA-00904: TIMES:
 invalid identifier'.  Here's the query that GeoServer is doing that
 returns the error:
 
 SELECT
 GW_LEV_PK,AGENCY_CD,SITE_NO,DATES,VALUE,REMARK,REMARK_DS,SOURCE_CD,METHOD_CD,METHOD_DS,QW_ACCURACY,QW_ACCURACY_NM,HOST,DBNUM,DWH_INSERT,LEV_CN,LEV_CR,LEV_MN,LEV_MD,MP_LEV_VA,SL_LEV_VA,LEV_ENT_CD,LEV_STATISTICS_CD,LEV_STATISTICS_NM,DATE_ACY_CD,SL_DATUM_CD,LEV_PARTY_TX,LEV_WEB_CD,LEV_AGENCY_CD,LEV_MPNT_SEQ_NU,LEV_RMK_TX,LEV_EQPID_TX,DWH_SITE_ID,PARAMETER_CODE,SOURCE,VALUE_ALL,AGENCY_CD,SITE_NO,DATES,VALUE,STATUS_CD,STATUS_DS,SOURCE_CD,METHOD_CD,METHOD_DS,QW_ACCURACY,QW_ACCURACY_NM,HOST,DBNUM,DWH_INSERT,LEV_CN,LEV_CR,LEV_MN,LEV_MD,TIMES,MP_LEV_VA,SL_LEV_VA,LEV_ENT_CD,LEV_STATISTICS_CD,LEV_STATISTICS_NM,DATE_ACY_CD,SL_DATUM_CD,LEV_PARTY_TX,LEV_WEB_CD,LEV_AGENCY_CD,LEV_MPNT_SEQ_NU,LEV_RMK_TX,LEV_EQPID_TX,DWH_SITE_ID
 FROM GWSI_LEVELS WHERE SITE_NO = ?
 
 The problem is that the GWSI_LEVELS table doesn't have a column called
 TIMES.  All of the other columns are correct (even though most