Thanks a lot, Russell!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROT
On Sun, May 11, 2008 at 4:36 PM, Николай Бульба <[EMAIL PROTECTED]> wrote:
>
>
> 2008/5/11 Peter Melvyn <[EMAIL PROTECTED]>:
> >
> > On 5/11/08, phactor <[EMAIL PROTECTED]> wrote:
> >
> > > no keyword REFERENCES. Where is it?
> >
> > AFAIK, SQLite engine 'per se' does not support reference integri
2008/5/11 Peter Melvyn <[EMAIL PROTECTED]>:
>
> On 5/11/08, phactor <[EMAIL PROTECTED]> wrote:
>
> > no keyword REFERENCES. Where is it?
>
> AFAIK, SQLite engine 'per se' does not support reference integrity, see:
>
> - http://www.sqlite.org/lang_createtable.html
> - http://www.sqlite.org/omitted
On 5/11/08, phactor <[EMAIL PROTECTED]> wrote:
> no keyword REFERENCES. Where is it?
AFAIK, SQLite engine 'per se' does not support reference integrity, see:
- http://www.sqlite.org/lang_createtable.html
- http://www.sqlite.org/omitted.html
HTH, Peter
--~--~-~--~~~--
Hello everyone!
I've got a strange behaviour of manage.py. Main thing is: not always
my models that use models.ForeignKey as field can be right transformed
to sql query for sqlite3. I've checked versions 0.96 and subversion.
Simple steps to reproduce:
1. django-admin.py startproject testproject
2
5 matches
Mail list logo