EOAttribute.validateValue question
EOAttribute.validateValue question
- Subject: EOAttribute.validateValue question
- From: Kieran Kelleher <email@hidden>
- Date: Wed, 11 Jul 2007 20:00:34 -0400
| Hi All, (quiet list last 2 days?)
As we know this EOAttribute.validateValue(...) gets called before custom eo validate<AttributeName> methods and it uses the class description to validate and/or do basic conversion. What are the alternatives to find an elegant way to call my custom validate first or is there none?
Why do I want to do this? I am importing text data from CSV files and pushing the text values into attributes in an efficient way, however I can easily handle conversion of YES/NO, T/F, Y/N, Y/null or TRUE/FALSE strings to Boolean in my custom validate<BooleanAttribute> methods, but of course EOF gets a shot at it first when I iterate through the imported values calling eo.validateTakeValueForKeyPath(aValue, aKey);
I have an alternative in mind, but just wanted to check with the smart folks first .... any suggestions?
I am thinking overriding validateValueForKey in ERXEntityClassDescription is also a possibility ..... any others?
Regards, Kieran |
_______________________________________________
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