On Jan 31, 2:31 am, Malcolm Tredinnick
wrote:
> On Sat, 2009-01-31 at 12:20 +1100, Malcolm Tredinnick wrote:
> > On Fri, 2009-01-30 at 09:49 -0800, mucisland wrote:
> > > Hi all.
>
> > > If I specify the ForeignKey target model as a string because it is not
> > > yet defined, the (SQLite3) SQL ta
On Sat, 2009-01-31 at 12:20 +1100, Malcolm Tredinnick wrote:
> On Fri, 2009-01-30 at 09:49 -0800, mucisland wrote:
> > Hi all.
> >
> > If I specify the ForeignKey target model as a string because it is not
> > yet defined, the (SQLite3) SQL table entry misses the REFERENCES
> > specifier. Example
On Fri, 2009-01-30 at 09:49 -0800, mucisland wrote:
> Hi all.
>
> If I specify the ForeignKey target model as a string because it is not
> yet defined, the (SQLite3) SQL table entry misses the REFERENCES
> specifier. Example:
SQLite doesn't support "references" constraints. So we don't bother
wr
Hi all.
If I specify the ForeignKey target model as a string because it is not
yet defined, the (SQLite3) SQL table entry misses the REFERENCES
specifier. Example:
class Department(models.Model):
head = models.ForeignKey('Person', related_name='heads')
class Person(models.Model):
departm
4 matches
Mail list logo