[EMAIL PROTECTED] schrieb:
Hi Greame,

Thanks for your efforts again.

--- Check the result mapping for the 'lastLogin' property.
--- Cause: com.ibatis.common.exception.NestedRuntimeException:
Error
setting properties of 'BaseObject [107, null, null, null]'.  Cause:
java.text.ParseException: Unparseable date: "1975-01-15"
According to this 'lastLogin' is of type 'datetime' but is
receiving a 'date' formatted result which  means it's receiving
the wrong column value when deployed on the remote server.

I think the two errors are unconnected. The unparseable 'date' shown is
from the dob column not the lastLogin column. I think that is a red
herring. I have no idea why 'lastLogin' is causing an issue as well.


I can't see why this would help since User.userResult has column
mapping but change

 <statement id="getUserByEmailAddress" resultMap="userResult"
parameterClass="string">
   select * from User where emailAddress = #value#
 </statement>
to

select id, title, firstName, lastName, gender, dob, telephoneNumber,
emailAddress, password, newsletter, preferredCurrency, activationKey,
activated, lastLogin  from User where emailAddress = #value#

You are right - no effect when the change made I'm afraid :-(

Back to the drawing board again I think. I appreciate your help here -
thanks again!

Andrew
Have you actually looked at the data the jdbc driver gives you from your database? DO this for both servers and compare. Maybe the issue lies somewhere between iBatis and the Database.

Regards
Stefan

Reply via email to