On Wednesday, October 30, 2002, at 02:58 AM, Micka�l Guessant wrote:
Could you please create a bug entry in Bugzilla for this ?
Done: it is bug 1093. http://bugzilla.exolab.org/show_bug.cgi?id=1093
Thanks, Rhett ===================================================== | Rhett Sutphin | Research Assistant (Software) | Coordinated Laboratory for Computational Genomics | and the Center for Macular Degeneration | University of Iowa - Iowa City, IA 52242 - USA | 4111 MEBRF - email: [EMAIL PROTECTED] =====================================================
<pages of backlog snipped>Rhett Sutphin wrote:Hi again,
I believe I've got a solution. First, forget about modifying org.exolab.castor.jdo.engine.SQLTypes -- the appropriate TypeConvertors are already defined there (in version 0.9.4, at least) -- I just missed them the first time through.
----- FAST & CLEAN SOLUTION
Now, having written the below, I just discovered a cleaner faster solution that doesn't involve modifying any of castor's code. Here's how: it occurred to me to wonder why the TypeConvertors were already defined if they weren't being used. Then I remembered that the type attribute of the field element is optional -- for type-checking only. So I reverted my changes and dropped the type attribute from all org.exolab.castor.types.Date fields.
It worked fine.
I suppose that this behavior should either be submitted as a bug or listed in the FAQ -- it is certainly counterintuitive that providing additional (correct) type-checking could break a system. Or am I misunderstanding something?
So, I'm leaving the following because I already wrote it, and it might help someone else.
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
