Aha! Then, I would suggest redesigning MigrationRecorder to only make the
table when an actual recording operation is done, and have it swallow the
table not existing as "no migrations applied" the rest of the time, if
people think that seems sensible.
Andrew
On Thu, Jan 22, 2015 at 10:44 AM,
Hey,
as soon as the MigrationRecorder is used there is a call to "ensure_schema"
that forces the creation of the migration table. The runserver command
(among others?) checks for unapplied migrations and thus creates the
migration table.
/Markus
On Wednesday, January 21, 2015 at 12:36:47 AM
Hi again,
Well, I can acknoledge that your reasons for list (beginner friendly) are
as good as my reasons for tuples (seems to be more logical choice for
things that are static). To say it in other words, my idea was simply: Use
tuples and the programmer will know that these arn't ment to be
