Opened 10 years ago

Closed 10 years ago

#22902 closed New feature (needsinfo)

"No changes detected" with SQLite, wrong answer

Reported by: d.kzlv.ru@… Owned by: nobody
Component: Migrations Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

If you make any changes, that SQLite doesn't allow to change via ALTER sql statement, Django shouldn't say "No changes detected", but it should say "You're using a piece of chick, so we cannot ALTER your changes".

Change History (4)

comment:1 by Tim Graham, 10 years ago

Which changes are these?

comment:2 by Dan <d.kzlv.ru@…>, 10 years ago

For example, changing name of a field.

comment:3 by Tim Graham, 10 years ago

I'm not sure how to produce the behavior you're describing. For example if I change the Choice.votes field in the tutorial to vote, I get the following prompt:

$ python manage.py makemigrations polls
Did you rename choice.votes to choice.vote (a IntegerField)? [y/N] y
Migrations for 'polls':
  0002_auto_20140625_1306.py:
    - Rename field votes on choice to vote

SQLite does have some documented caveats, but as far as I know, the autodetector behavior is independent of the database you are using.

comment:4 by Aymeric Augustin, 10 years ago

Resolution: needsinfo
Status: newclosed
Note: See TracTickets for help on using tickets.
Back to Top