On Friday, February 22, 2013 11:27:59 PM UTC-7, Skylar Saveland wrote: > > This is still a good question :) >
The answer is that there is no way to instruct Django that you really, truly want this CharField to be NOT NULL even on Oracle, and that is unlikely to change. Part of the philosophy in the development of the Oracle backend was that Oracle DBAs would not likely be running syncdb directly, but that devs would be more likely to run sqlall and hand-edit the scripts as needed (e.g. to add storage clauses) before handing them off to the DBA. As a result of this thinking, not every possible Oracle idiosyncrasy is directly addressable via model options, and we are reluctant to add general features that are only useful for Oracle. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
