Hi,
I have some Python code that generates initial data for some of my
tables; I currently call that code from a post_syncdb hook. In Django 1.3, it
looks like Django now calls TRUNCATE (or an equivalent non-PostgreSQL-ism) on
all tables after running syncdb and all of its post- hooks. I know I could use
fixtures, but it's much more readable for us to use Python code for this
initial data. (The data being generated is somewhat complex and denormalized
for various reasons that probably won't be changed just for the sake of this
issue..., but there are nice clean simple Python functions to create each
entry.) Is there a good way to do so in the brave new Django 1.3 world?
Thanks,
Adam
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
