Re: MyISAM vs InnoDB; was Django 1.2.1 strange problem

2011-12-16 Thread Joey Espinosa
Right, thanks for the correction! -- Joey "JoeLinux" Espinosa Software Developer http://about.me/joelinux On Dec 16, 2011 9:15 AM, "Tom Evans" wrote: > On Fri, Dec 16, 2011 at 1:44 PM, Joey Espinosa > wrote: > > I think it's also worth

Re: MyISAM vs InnoDB; was Django 1.2.1 strange problem

2011-12-16 Thread Tom Evans
On Fri, Dec 16, 2011 at 1:44 PM, Joey Espinosa wrote: > I think it's also worth noting that MyISAM doesn't support foreign keys, > which would make the object relationships that Django creates impossible. > MyISAM supports foreign keys just fine, it just doesn't

Re: MyISAM vs InnoDB; was Django 1.2.1 strange problem

2011-12-16 Thread Masklinn
On 2011-12-16, at 14:44 , Joey Espinosa wrote: > I think it's also worth noting that MyISAM doesn't support foreign keys, > which would make the object relationships that Django creates impossible. That's not correct, the relationships are there (it's just tags between two columns), they're just

Re: MyISAM vs InnoDB; was Django 1.2.1 strange problem

2011-12-16 Thread Joey Espinosa
I think it's also worth noting that MyISAM doesn't support foreign keys, which would make the object relationships that Django creates impossible. -- Joey "JoeLinux" Espinosa Software Developer http://about.me/joelinux On Dec 16, 2011 8:40 AM, "Sells, Fred" wrote:

MyISAM vs InnoDB; was Django 1.2.1 strange problem

2011-12-16 Thread Sells, Fred
Thanks for such a clear and helpful response. I'll begin the upgrade migration immediately. I noticed that a newer project does use InnoDB, yet I don't see anything in settings.py which specifies the engine in either project. It's been a while but the original project was built with Dj 1.2 and