Opened 12 years ago
Closed 12 years ago
#18734 closed New feature (wontfix)
initial_data for debug only
Reported by: | DataGreed | Owned by: | nobody |
---|---|---|---|
Component: | Uncategorized | Version: | 1.4 |
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
I am sorry, I am not sure if Trac is the right place for feature requests, but anyway.
I suppose there should be some name pattern implemented, for loading fixtures of initial data only if debug is set to true.
Like initial_debug_data for example.
Note:
See TracTickets
for help on using tickets.
I'm afraid I don't see why this would be a useful feature.
Firstly, I'm not sure I see the use case for "debug only" initial data. The only case that I can see where it *might* be useful is as something to differentiate development/production; but in that case, I'd argue the better option would be to have a different fixture for each of the two scenarios, loaded as an explicit request.
Secondly, I'm not convinced that a DEBUG setting is the best thing to use as a trigger for whether data is loaded. The value of DEBUG isn't tied to the synchronization process, so you could very easily sync with DEBUG=False, then set DEBUG=True, and you won't get anything loaded unless you run syncdb again.
Lastly, if you want to have a fixture called initial_debug_data, you can -- the only difference is that it won't be automatically loaded like initial_data.
Marking wontfix; if you want to make your case, start a discussion on django-developers and see if you can convince anyone that the idea is worth pursuing.