Re: Re: initial value of required fields
Sebastien Bigaret <[email protected]> 21 Jul 2004 19:34:35 +0200
| Newsgroups | gmane.comp.python.modeling |
|---|---|
| Message-ID | <[email protected]> |
John Lenton <[email protected]> wrote: > On Wed, 21 Jul 2004 12:17:42 -0300, John Lenton <[email protected]> wrote: > > Sébastien, would having an option for required fields being > > initialized to non-null values be ok with you? > > > > In a project I'm overseeing the team finds it unnatural that a > > required field that isn't filled in won't raise an exception, and I > > thought the easy way out (while I thump them with a > > validate-everything stick) would be to make it optional... Sorry, but I'm not sure to understand: are you facing situations where objects with None value in required field did not make ec.saveChanges() raise? > FWIW, now they're using defaultValue to do the same thing... and maybe > that's enough. If tyhis is just a matter of initialization then yes, the default values should be enough, or am I missing something? -- Sébastien. ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21&alloc_id040&op=click