On 5/17/2011 11:31 AM, Jeremy Dunck wrote:
On Tue, May 17, 2011 at 10:24 AM, Ned Batchelder<[email protected]> wrote:
Maybe it wouldn't be so bad to punt on invalidation? The cached databases
would only have to be rebuilt if the models changed or if the fixtures
changed, right? We have a similar situation now with migrations: you have
to write one every time you change a model, and there's no automatic
mechanism that kicks in to tell you to write one, you just have to know:
"change a model, write a migration." If that's working now, then what's
wrong with, "change a model or a fixture, re-run the test database cacher."
The difference is, migrations can be merged. Database cache is local
state. No?
Hmm, that's a good point.
--Ned.
--
You received this message because you are subscribed to the Google Groups "Django
developers" 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-developers?hl=en.
