Hi again, > > Hello, > > Way back in OJB 0.9.7 I brought this issue up and I don't > think I got much response. I took an OJB hiatus for a while > and now I'm back and have run up against this problem again. > The problem is that when I insert a record, OJB tries to > insert null values into fields that I did not explicity set > in my object. So if I have specified default values in my > database field, which I do quite a bit, those default default > values never get used because the query that OJB generates is > telling the database to explicitly set those fields to null > instead of omitting those fields and letting the db handle it. > > I find it really hard to believe that I'm the only one that > has issues with this... but I don't see much discussion on > it. Am I missing something obvious or does anybody have any > good workarounds (besided implementing default values on the > application/bean side) or has it been addressed in 0.9.9?
This is still not addressed in 0.9.9 and later! You can avoid writing to db columns by not providing a field-descriptor for the attribute in question. You could either change an existing class-descriptor at runtime, to add/remove field-descriptors, or use different repositories for read and write phases. cheers, Thomas > > Thanks! > > > > --------------------------------- > Do you Yahoo!? > Yahoo! Tax Center - forms, calculators, tips, and more > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
