#1828: sqlreset forgets foreign key constraint to outer world
------------------------------+---------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: Database wrapper | Version:
Severity: normal | Keywords:
------------------------------+---------------------------------------------
when isseuing syncdb a different database schema is created than with
sqlreset. one difference is that foreign key constraints are not created
when the model comes from another application. another difference are the
additional indexes (i.e. on slug fields) which are not created. this is my
test:
{{{
(cd $(PROJ); PYTHONPATH=`pwd`/.. ./manage.py sqlreset myapp) |
sqlite3 $(PROJ).db
sqlite3 $(PROJ).db .schema > $(PROJ).sql
}}}
against:
{{{
(cd $(PROJ); PYTHONPATH=`pwd`/.. ./manage.py syncdb)
sqlite3 $(PROJ).db .schema > $(PROJ).sql
}}}
done each with no existing database
--
Ticket URL: <http://code.djangoproject.com/ticket/1828>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
