Is this a bug on Bentley Geospatial administrator on Date and Dateticks for database?

Re: Is this a bug on Bentley Geospatial administrator on Date and Dateticks for database?

cdalesandro — Fri, 25 Jun 2010 17:06:58 GMT

Hi Jun,

Would you please send your XFM schema and specify the problem feature definition?

Regards,

Chris

Re: Is this a bug on Bentley Geospatial administrator on Date and Dateticks for database?

aarrjeeli_001 — Fri, 25 Jun 2010 04:04:50 GMT

Hi Jerry,

Thanks for the reply

Is this a Oracle Spatial or regular Oracle connection ? This is a regular Oracle connection not an Oracle Spatial.

How was the date field defined in the database ? I suspect as just DATE, but there are other options. Yes its just a DATE, and according to our database administrator there is no other option, in the database field creation in Oracle TIME is already part of the DATE/TIME format. But, if you have suggestions I would be glad to hear that.

Are you creating the SQL statement or is the GSA creating it when you tell it to via the Add SQL Statements for the paticular feature ? I am not creating the SQL statements in the GSA its the GSA creating it via the Add SQL Statements, only I take out the # in the statement because # is not recognized in Oracle database.

Jun

Re: Is this a bug on Bentley Geospatial administrator on Date and Dateticks for database?

Jerry Walter - Bentley — Thu, 24 Jun 2010 16:27:51 GMT

Couple of questions ????

Is this a Oracle Spatial or regular Oracle connection ?
How was the date field defined in the database ? I suspect as just DATE, but there are other options.
Are you creating the SQL statement or is the GSA creating it when you tell it to via the Add SQL Statements for the paticular feature ?

Thanks !

Jerry

Re: Is this a bug on Bentley Geospatial administrator on Date and Dateticks for database?

aarrjeeli_001 — Thu, 24 Jun 2010 05:12:43 GMT

Hi Jeff and Jerry

Any comment for this?

Jun