Edson Carlos Ericksson Richter wrote:
It's not a OJB problem. I'm just looking if OJB could help me find bugs introduced from any programmer here.
Sample: I have a class with 5 relations updatables, and when I execute insert, maxdb answer "[-5005] Missing non null value". Besides OJB tell me what bean he is trying to persist, it's difficulty to find what field that messed up.
If I tell "nullable='true'" and "nullable='false'" (or something like), then OJB warn me if he finds the field is NULL (when nullable='false') could be a bigger step searching for this kind of app bug.
Nothing that I can't debug and try to find using a trace or P6Spy, but in a schema with more than 200 tables, 2000 fields, and 1400 classes, it definitelly could be easier.
Hmm, that might be possible by adding a nullable property to the field descriptor and checking it in the persistentfield impls. I'll check that.
For now, you could try using a 'pass-through' field conversion that does nothing but checking the value for null.
Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
