Re: M2M Column Names Changed in 1.2 - Breaks Backwards Compatibility

2010-01-14 Thread Russell Keith-Magee
On Thu, Jan 14, 2010 at 3:13 PM, simonb wrote: > I think this ticket http://code.djangoproject.com/ticket/12386 > identifies a change in the m2m code which breaks backwards > compatibility. Hi Simon, I'm aware of the ticket - there are a couple of tickets that I need to take a look at regarding

Re: M2M Column Names Changed in 1.2 - Breaks Backwards Compatibility

2010-01-14 Thread Harro
Hmm where did the foreign key go on the 1.2 example? And I must say that the name for the modelc column is a bit weird. On Jan 14, 8:13 am, simonb wrote: > I think this tickethttp://code.djangoproject.com/ticket/12386 > identifies a change in the m2m code which breaks backwards > compatibility.

M2M Column Names Changed in 1.2 - Breaks Backwards Compatibility

2010-01-13 Thread simonb
I think this ticket http://code.djangoproject.com/ticket/12386 identifies a change in the m2m code which breaks backwards compatibility. Consider the following three apps and models: AppA/models.py: class ModelA(models.Model): name = models.CharField(max_length=1024, default='', blank=True)