Skip to content
This repository was archived by the owner on Apr 21, 2021. It is now read-only.

Conversation

maraujop
Copy link
Contributor

I have worked on a bugfix for this issue. I haven't provided tests, although I know I should :) If you like my code and I can work on them.

Regards,
Miguel Araujo

… or some other specific database backend magic that sqlite3 is not able to reproduce. Therefore syncdb command fails at generating the tables in the database.

I have added a --default option that will use default project settings
and generate test databases, that will use for populating the fixtures.

TODO: Maybe it's a good idea that the user can provide a test_settings
file as a parameter. So he can use specific settings for generating
the databases.
@maraujop
Copy link
Contributor Author

maraujop commented Nov 3, 2010

Please review my last commits. I have improved the way I was handling --default optparse option.

@maraujop
Copy link
Contributor Author

Questions, comments, tomatoes ???!!

@jjmaestro
Copy link

@alex Are you planning on reviewing this pull request at all? it fixes your django-fixture-generator for GeoDjango which is quite needed IMHO. And it's been stalled for over a year...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants