Russell Keith-Magee wrote:
> You are correct (and it's not just with MySQL). This is a bug born of
> the way that syncdb installs applications. For some reason, it doesn't
> defer to install - it duplicates the install logic, but doesn't include
> indexes.
>
> I intend to refactor this code wh
On 8/24/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
It looks like syncdb has a bug in that it doesn't create the indexes --at least on MySQL.
You are correct (and it's not just with MySQL). This is a bug born of the way that syncdb installs applications. For some reason, it doesn't defer to in
The tutorial says and mentions that it creates indexes explicitly.
The syncdb command runs the sql from 'sqlall' on your database for all
apps in INSTALLED_APPS that don't already exist in your database. This
creates all the tables, initial data and indexes for any apps you have
added to your pro
Yes, that worked.
But the documentation always seems to recommend running ./manage.py
syncdb after you set up your models. It should also create any indexes
you have defined.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Googl
try ./manage.py install, it executes sqlall
Corey
On Aug 23, 2006, at 2:42 PM, [EMAIL PROTECTED] wrote:
>
> I've got the following:
>
> class Page(models.Model):
> name = models.CharField(maxlength=64, db_index=True,
> unique=True)
> description = models.TextField(blank=True)
>
I've got the following:
class Page(models.Model):
name = models.CharField(maxlength=64, db_index=True,
unique=True)
description = models.TextField(blank=True)
class Text(models.Model):
page = models.ForeignKey(Page, db_index=True,
edit_inline=models.STACKED)
conte
