johnf wrote: > On Sunday 17 February 2008 11:41:37 am Uwe Grauer wrote: >> johnf wrote: >>> On Sunday 17 February 2008 11:09:42 am Ed Leafe wrote: >> >> ... >>>> What if I were to add code that said that if biz.DefaultValues = None >>>> (instead of an empty dict), all the non-PK values would be assigned >>>> values of None? I haven't tested it or anything; just throwing out >>>> ideas. >>>> >>>> -- Ed Leafe >>> That sounds great for the postgres guys but if memory serves it doesn't >>> work the same way for FireBird. At least that's what I got from Uwe's >>> post from several months ago. >> Can you please specify what exactly you think doesn't work for firebird? >> >> Uwe > Maybe I'm wrong but I thought there was some issue with "<None>", > Python "None", vs FireBird NULL. I thought you said something to effect > that python "None" <> FireBird NULL? Which caused you to code the default > somehow. I know next to nothing when it comes to FireBird.
There was an issue with datefields, which got a default value (today). I had to set a defaultvalue for the datefields to make dabo stay out of the way for datefields which didn't get entered by the user. In general dabos behavior regarding NULL values seems to wrong. Every textcontrol gets set to '' which makes the database setting "not null" nearly useless. NULL is a state and not a value. Dabo shouldn't touch fields where the user doesn't enter a value. I see dabos behavior as a major bug. All this has nothing to do with firebird. Firebird/interbase supported enterprise level features at a time when mysql and postgresql wasn't grown up (or even existed?). Uwe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
