Ticket #174 (closed enhancement: fixed)

Opened 5 years ago

Last modified 5 years ago

Initial creating/filling of database needs better documentation

Reported by: Robert <trebor74hr@…> Owned by: andrew
Priority: major Milestone:
Component: documentation Version:
Keywords: Cc:

Description

The normal south scenario build from the start is:

  • database without tables
  • south migrate
  • will start with initial migration which will do
    • create tables based on initial south migration (the oldest db scheme)
    • call "classic" django initial load of data (fixtures/initial.json|xml)
  • will start next "normal" migration - change scheme, fill data, etc.
  • will start next ... - will repeat that until last "normal" migration

The important thing here is (correct me if I'm wrong):
initial fixture should be compatible and prepared only for initial south migration's database scheme

If this is so or not, please fill documentation with information which explain how things work in south for this case. Thanks.

Change History

comment:1 Changed 5 years ago by Robert <trebor74hr@…>

Note that ticket #170 suggests is enhancement that enables creation of db from the scratch by running "classic" django syncdb and faking all migrations. In this case initial fixture is different from normal south initial fixture (based on diff schemes). Check http://south.aeracode.org/ticket/170#comment:3.

comment:2 Changed 5 years ago by andrew

  • Status changed from new to closed
  • Resolution set to fixed

No, this isn't how it works. initial_data is loaded _after_ all migrations have run, as it's supposed to be up to date, whereas if you want the behaviour you described, you have to call the load_data in one of the first migrations. I'll update the docs to be more explicit.

Note: See TracTickets for help on using tickets.