[#4926] - Unable to use date filters in adHoc query. produces "literal does not match format string" in java stack trace

Posted by jadon on June 15, 2015 - 11:42pm
Category:
Bug report
 Priority:
Normal
 Status:
Feedback Requested
Project:
JasperReports® Server
 Severity:
Major
 Resolution:
Open
Component: Reproducibility:
Always
 Assigned to:
Subscribe

Any filter that uses date type field causes Oracle to produce an error ORA-01861: literal does not match format string.

AttachmentSize
Binary Data ora-01861-stacktrace.log16.33 KB
v6.1.0
jadon's picture
jadon
2
Joined: Dec 8 2014 - 7:11pm
Last seen: 7 years 7 months ago

6 Comments:

#1Posted by yuzvyaka on August 17, 2015 - 6:59am
  • Status:New» Feedback Requested

I can reproduce it too and it's really annoying: date filters just not working at least with oracle jdbc Data Sources. Is there any changes or plans to fix this past 2 month from original bug report?

#2Posted by kaustav.das007 on August 20, 2015 - 3:33am

When is this getting fixed? Having a lot of trouble as I am working with date filters!<strong><<<<<< This comment was blocked and unpublished because <a href="http://www.projecthoneypot.org/">Project Honeypot</a> indicates it came from a suspicious IP address.</strong>

#3Posted by jadon.smith on September 9, 2015 - 2:10am

It has been indicated to me that this will be fixed in the next release.

#4Posted by gsteiner on September 9, 2015 - 1:13pm

Here is a work around I received from support.

There is a workaround and to make this change, edit WEB-INF/applicationContext-semanticLayer.xml and look for the property "excludeFunctionTemplates" in the bean "defaultSQLGenerator".

Comment out the two <value> elements as shown:

<bean id="defaultSQLGenerator"
class="com.jaspersoft.commons.semantic.dsimpl.SQLGenerator" scope="prototype">
<property name="excludeFunctionTemplates">
<list>
<!-- <value>Integer</value> -->
<!-- <value>Timestamp</value> -->
</list>
</property>
<property name="functionTemplates">
<map>
...

#5Posted by jimw on September 18, 2015 - 5:04pm

In the workaround above, you should uncomment the Integer value:

<value>Integer</value>

Otherwise, you may get this exception if you have a numeric field set to "Dimension" in a domain.

java.lang.RuntimeException: groovy evaluation failed on string args[0].value and expression Integer(24)

#6Posted by jimw on September 18, 2015 - 5:07pm

Also try this setting in the driver URL.

FetchTSWTZasTimestamp=true

Feedback
randomness