Proposal: Database Constraints

Some years ago, I discussed adding database-level check constraints into django: https://groups.google.com/forum/#!topic/django-developers/OJN5kpcseAg There is also an issue: https://code.djangoproject.com/ticket/11964 I'm thinking about revisiting this, and wanted to get some discussion going

Re: [GSOC] Introduction and task proposal

Hi Josh, Sorry for getting back now. I have just finished my exam session, so I will be trying out the djangocore-box VM. Regards, Daniel Pyrathon On Thursday, March 27, 2014 5:45:36 AM UTC+1, Josh Smeaton wrote: > > If you haven't already got all your databases installed on your >

ORM and admin

It is rather late in the day to bring this up but ... should we remove ORM and admin from Django core? Thanks, Pradip P Caulagi -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from

Re: ORM and admin

April fools eh? -- You received this message because you are subscribed to the Google Groups "Django developers" 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

Re: Proposal: Database Constraints

Hmm, I'm not sure about this. On the one hand, during the migrations work I refactored check constraints for the existing stuff (e.g. PostitiveIntegerField) out of the type string and into a separate check constraints string, so some of the work is already there, especially around making sure

Deprecating Widget Media class

There's been some discussion in ticket #22298about deprecating the widget Media class. If this would make you particularly happy or sad, please leave your feedback on this thread or on the ticket. -- You received this message because you are

Re: Deprecating Widget Media class

In my experience using the Media class is really only helpful in one place: the admin. If you have a third-party widget which requires CSS or JS is a pain to include it without the use of Media. Users want to just include the widget in the form class and have it "just work". A majority of the

Re: Proposal: Database Constraints

Hi Just FYI: back in 2007 GSOC there was a project to add constraints. The syntax was as follows: class Manufacturer(models.Model): mfg_name = models.CharField(maxlength=50) car_sale_start = models.DateField() car_sale_end = models.DateField() quantity_sold = models.IntegerField() car_price =

Re: Proposal: Database Constraints

On Wednesday, April 2, 2014 3:35:24 AM UTC+10:30, Andrew Godwin wrote: > > Hmm, I'm not sure about this. On the one hand, during the migrations work > I refactored check constraints for the existing stuff (e.g. > PostitiveIntegerField) out of the type string and into a separate check >