I'll move to Abator 1.0 on next days!
Thanks,
aris
Jeff Butler wrote:
That's very interesting - and you did a lot of work on this!
I'm no Oracle expert, but I did a google search too and found some others
reporting similar issues related to slow queries when using
setTimestamp. So, barring so
That's very interesting - and you did a lot of work on this!
I'm no Oracle expert, but I did a google search too and found some others reporting similar issues related to slow queries when using setTimestamp. So, barring someone else's ideas, I think you're probably doing the right thing with th
Thank you Jeff for your reply, I'll try Abator 1.0 but probably I
haven't well explained the problem.
I like the way Abator generates xml mappings and domain objects and I
think it's right to set the oracle Date as (jdbc) TIMESTAMP (if set to
(jdbc) DATE then hours, minutes and seconds are los
Here are a couple of thoughts:
1. Oracle's DATE type can be DATE, TIME. or TIMESTAMP depending on how it's configured. But I think their JDBC driver always reports it as TIMESTAMP - so that's why Abator generated it as TIMESTAMP. If it really is a DATE then use a to force the field to jdbcTyp
Hi all,
I'm new to this mailing list and to Ibatis too.
Today I wrote my first type handler callback class to solve a problem
with the Oracle jdbc driver (from version 9).
I've a table with a column of type DATE and an index is defined on this
column. The table is mapped from a domain object
