Re: EOQualifier timestamp comparison help [i.e., exception]
Re: EOQualifier timestamp comparison help [i.e., exception]
- Subject: Re: EOQualifier timestamp comparison help [i.e., exception]
- From: LD <email@hidden>
- Date: Fri, 19 Aug 2005 09:47:41 +1000
Hi there,
On 19/08/2005, at 8:41 AM, Chuck Hill wrote:
Based on the stack trace:
java.lang.NullPointerException
at
com.webobjects.eoaccess.EOAttribute.adaptorValueByConvertingAttribute
Value(EOAttribute.java:2020)
at com.webobjects.jdbcadaptor.JDBCColumn.takeInputValue
(JDBCColumn.java:562)
at
com.webobjects.jdbcadaptor.JDBCChannel._bindInputVariablesWithBinding
sAndExecute(JDBCChannel.java:226)
at com.webobjects.jdbcadaptor.JDBCChannel._evaluateExpression
(JDBCChannel.java:303)
I'd look in the model for the problem. Missing a column name,
wrong external data type, wrong value type? Something wrong at the
entity level?
Yeah, I'd checked and doubled checked the model via vexModeler ;-)
Looking in the actual Puchase.plist, I see:
{columnName = TIMESTAMP; name = timestamp; prototypeName = dateTime; }
So, I've updated that to:
{columnName = "TIMESTAMP"; name = timestamp; prototypeName = dateTime; }
But still no joy :-/
Do you see any problems here?
The prototype dateTime is as follows:
{
allowsNull = Y;
columnName = "";
externalType = timestamp;
name = dateTime;
valueClassName = NSCalendarDate;
valueType = T;
},
Looking forward to when some serious Bug Bomb is utilised within
EOModeler...
with regards,
--
LD
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden