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.

Thankyou for fast reponse,

Edson Richter


Thomas Dudziak escreveu:

Edson Carlos Ericksson Richter wrote:

I having several problemas with database in NULL values area.
If I inform in XML what fields allow XML and what not, OJB will warn me if I forgot to fill some field? If yes, is this a sanity check that can be enabled/disabled?


Could you give an example ?

Tom


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to