On Thu, Mar 12, 2009 at 6:44 AM, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > > On Thu, Mar 12, 2009 at 8:54 AM, Chris <chriss...@gmail.com> wrote: >> >> I'm using Django 1.0.2, and I dumped out a sample database as XML >> using dumpdata. When I run my unittests using this XML as a fixture, I >> get the error: > ... >> SAXParseException: <unknown>:20:41: unbound prefix >> >> This error seems to be caused by <gd:email> tags, like: >> >> <property name="email" type="gd:email"><gd:email >> address="j...@doe.com" /></property> >> >> Why is Django having problems parsing its own XML? Removing the "gd:" >> seems to silence the error, but how can I get Django to output valid >> XML that won't break the unittests? > > I'm a little confused as to where "gd:email" would have come from in > the first place. For that matter, the <property> tag is a little > confusing too. > > You say this is a file produced by Django 1.0.2 dumpdata in XML mode - > if this is the case, the fixture should follow some thing like the > following format: > > <?xml version="1.0" encoding="utf-8"?> > <django-objects version="1.0"> > <object pk="2" model="fixtures.article"> > <field type="CharField" name="headline">Poker on TV is great!</field> > <field type="DateTimeField" name="pub_date">2006-06-16 11:00:00</field> > </object> > <object pk="5" model="fixtures.article"> > <field type="CharField" name="headline">XML identified as > leading cause of cancer</field> > <field type="DateTimeField" name="pub_date">2006-06-16 16:00:00</field> > </object> > </django-objects> > > It shouldn't be outputting <property> tags, and the 'type' attribute > should be an internal Django type identifier (CharField, etc). If > you're getting something else, this is highly confusing. > > The only ways I can see that you could be getting a different output is if: > 1) You have installed a custom serializer that is overriding the > default XML serializer > 2) You are using a custom field definition that is providing bad data > to the serializers > 3) You are doing some sort of XML processing on the fixture that is > messing with things. > > Given that you have sent a later email that reports similar problems > with JSON fixtures, (2) seems the most likely option. > > However, to diagnose any further, we're going to need some more > details - in particular, a copy of a fixture file and the model > definition that produced the dump. > > Yours, > Russ Magee %-)
I suppose I should have mentioned I'm using App Engine Patch, which is likely defining the custom fields you're seeing. I'll post these questions in their forum to see if they have any ideas. Chris --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
