I asked this before and no one answered, but after having to do this manually in the shell for about the fifteenth time, I'm going to ask again.
Is there a way to add user permissions to a test fixture that isn't brittle? Let me outline what I'm doing and see if I'm doing something wrong: 1. I serialize the database with permission data and the permission is stored as a foreign key, which means the serialized data just includes its id. 2. I use the test data for a while, very happily. 3. I add a new app to my project, which has its own permissions (or even maybe just change the order my apps appear in INSTALLED_APPS). This last step changes the id of the old permissions and my serialized test data no longer sets the permissions it's supposed to. Now I have to remake my test data. Is this a real problem, or am I just making it up? If it's a real problem, is there a way around it? Since fixtures are such an easy way to create test data, it would seem a really good idea if they supported the ability to create data that wouldn't break unnecessarily as a result of a project just evolving. Hoping for some way to avoid "from django.contrib.auth.models import User, Permission" over and over again in the shell, Todd --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
