Specifying "through" instead of "db_table" did not raise any errors,
but it caused the relevant field in the admin change form to
disappear!
On Apr 3, 4:52 pm, Karen Tracey wrote:
> On Fri, Apr 3, 2009 at 4:25 PM, Andrew G. wrote:
>
> > The following code in a
wrote:
> On Fri, Apr 3, 2009 at 4:25 PM, Andrew G. wrote:
>
> > The following code in a fresh project/app will cause the database
> > creation to fail.
>
> > class Position(models.Model):
> > description = models.CharField(max_length=20, blank=
arams)
pysqlite2.dbapi2.OperationalError: table "part_positions" already
exists
The django project I am working with is mapped to an existing
database, so this only causes a problem when tests are run, since the
test system creates its temporary database.
On Apr 2, 7:42 pm, Russell Keith
g table intact. This will duplicate data
> though - are these highly accessed tables?
>
> I think.
>
> -Adam
>
> On Apr 2, 9:23 am, "Andrew G." wrote:
>
> > I have a django app that is built against an existing database. In
> > the database, there are a cou
I have a django app that is built against an existing database. In
the database, there are a couple tables used as the many-to-many
relation lookup table. However, I have mapped models to the many-to-
many lookup table, since I have a need for accessing these entries
directly. Since the tables
5 matches
Mail list logo
