We are running 5.0 against an Oracle database.
When Yellowfin reads in the Date field, it recognized it as a Timestamp instead of a Date.
This is disruptive when the field is used in filters as it is forcing the entry of time when doing a > or = operation.

Is there any way to force the view to recognize the field as a Date?
Can we change the defined type in an export of the view and re-import it?

Here is a snippet of the table create script for the table being accessed:
[code]
CREATE TABLE xxxx (
AD_ID NUMBER NOT NULL,
EVENT_DATE DATE NOT NULL,
IMPRESSIONS NUMBER NULL,
[/code]

and a screen cap showing the recognition of that field as a Timestamp.