Re: Oracle: blank, null, and empty_strings_allowed

On 6/20/2012 11:46 AM, Melvyn Sopacua wrote: On 20-6-2012 20:31, André Pang wrote: Right. There's currently no way to enforce required=True at the database level. So, your model clearly defines that it doesn't allow empty values, yet some were inserted? Can you pull this out of th

Re: Oracle: blank, null, and empty_strings_allowed

asically, enforce "required=True" at the database-level? On Tue, Jun 19, 2012 at 7:23 PM, Ian <mailto:ian.g.ke...@gmail.com>> wrote: On Monday, June 18, 2012 5:59:27 PM UTC-6, André Pang wrote: What I'd like to do is (1) disallow NULLs, and (2) disallow

Re: Oracle: blank, null, and empty_strings_allowed

ds/#null Anyways, if you don't allow NULL and you don't allow empty strings, what are you going to put in there when there's nothing? On Mon, Jun 18, 2012 at 7:59 PM, André Pang <mailto:andre.p...@gmail.com>> wrote: On Jun 18, 2012, at 4:05 PM, Ian wrote: >

Re: Oracle: blank, null, and empty_strings_allowed

On Jun 18, 2012, at 4:05 PM, Ian wrote: >> I'd assume that Django would only generate schemas where NULL is allowed for >> fields where blank=True, and that fields where blank=False would have "NOT >> NULL" included in the Oracle DDL. > > blank=True is a validation option, not a database option

Oracle: blank, null, and empty_strings_allowed

Hi all, The Django Oracle documentation has the following to say about NULL and empty strings (emphasis mine): Django generally prefers to use the empty string ('') rather than NULL, but > Oracle treats both identic

blank, null, Oracle, and empty_strings_allowed

Hi all, The Oracle database backend has the following note about NULLs vs empty strings (emphasis is mine): Django generally prefers to use the empty string ('') rather than NULL, but > Oracle treats both identically. To get around this, the Oracle backend > ignores an *explicit null option o