Hi Vackar, Thank you, now we are getting somewhere!
On Thursday, November 8, 2018 at 5:36:53 PM UTC+1, vaf...@exscientia.co.uk wrote: > > My main concern currently is that required fields are not enforced at the > db level, which makes using it with other clients difficult. I would much > prefer that constraints be added, and accept that empty strings cannot be > inserted into required columns. > Okay, now I get you. I have no strong feelings how our oracle backend should behave here; other than your suggested change would be (highly?) backwards incompatible and that alone might prevent it from getting merged. Maybe Felix can chime in here with his oracle knowledge. FWIW, Django has quite a few places where it does stuff in the framework itself instead of at the database level. Examples include the handling of database default values (we don't, defaults are in the application, even for simple integers and strings) as well as handling of cascades on deletes. If one cannot live with those issues, it is imo currently best to manage the database independent from Django. We are certainly open to improving in those areas though. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to firstname.lastname@example.org. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/94f68c2f-2639-4fe1-b552-a0f7a11f3509%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.