Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-30 Thread donarb
At this point, I would just skip trying to load the data through Django and write a quick Python script to load the data using INSERT statements or create a bulk data file to load it directly into MySQL. I'm not as familiar with MySQL as I am with Postgres, but Postgres can swallow a whole data

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-30 Thread Sam Raker
I've also tried changing the charset and collation options in my MySQL tables. Still no good. I'm so stumped. Can anyone help me, please? On Sunday, December 30, 2012 8:54:44 PM UTC-5, Sam Raker wrote: > > I tried changing my backend to django-mysql-pymysql ( > http://pypi.python.org/pypi/django-

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-30 Thread Sam Raker
I tried changing my backend to django-mysql-pymysql (http://pypi.python.org/pypi/django-mysql-pymysql/0.1), and that didn't work either. I'm really at my wits' end. Can anyone help? On Sunday, December 30, 2012 4:21:57 PM UTC-5, Sam Raker wrote: > > I just tried both of those things, and the YAM

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-30 Thread Sam Raker
I just tried both of those things, and the YAML data loaded fine, and validate said I had 0 errors. Any other suggestions? I'm really stumped here. On Sun, Dec 30, 2012 at 3:35 PM, donarb wrote: > > > On Sunday, December 30, 2012 11:58:46 AM UTC-8, Sam Raker wrote: >> >> So I upped the verbosit

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-30 Thread donarb
On Sunday, December 30, 2012 11:58:46 AM UTC-8, Sam Raker wrote: > > So I upped the verbosity like you said, and basically all it got me was a > bunch of text telling me all the places Django didn't find my fixture > before it finally did, and then the same error. Here's the full text of the >

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-30 Thread Sam Raker
So I upped the verbosity like you said, and basically all it got me was a bunch of text telling me all the places Django didn't find my fixture before it finally did, and then the same error. Here's the full text of the error: Traceback (most recent call last): File "/home/menusadmin/.pythonbrew

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-30 Thread donarb
On Sunday, December 30, 2012 9:54:45 AM UTC-8, Sam Raker wrote: > > Thanks for your suggestions. > > I eliminated the underscores and got rid of the __unicode__ methods > entirely, cleaned up my except statement, and changed the order of stuff > such that all of each model's fields are defined be

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-30 Thread Sam Raker
Thanks for your suggestions. I eliminated the underscores and got rid of the __unicode__ methods entirely, cleaned up my except statement, and changed the order of stuff such that all of each model's fields are defined before any methods. (As for the pk field: The csvs I'm using are actually dumps

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-30 Thread Amirouche
On Saturday, December 29, 2012 9:42:50 PM UTC+1, Sam Raker wrote: > > Here's the truncated version I tried to load in case the problem was the > length of the file: > - fields: {location: ST. DENNIS HOTEL, restaurant: Veterans American > Guard, status: complete, > year: 1900} > model: dis

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-29 Thread donarb
And your __unicode__ method is incorrect as well. You should be returning self.restaurant. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/bsJoTGDbveYJ. To

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-29 Thread donarb
Not sure if it's related to your problem, but you should never create function names like __period__. Names such as those are reserved for Python internals. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visi

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-29 Thread Sam Raker
Here's the truncated version I tried to load in case the problem was the length of the file: - fields: {location: ST. DENNIS HOTEL, restaurant: Veterans American Guard, status: complete, year: 1900} model: dishes.menu pk: 12495 - fields: {location: BOSTON, restaurant: New England Shorthan

Re: loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-29 Thread Ryan Blunden
Can you provide a single example of one of the fixture objects you're trying to import, as well as the model it corresponds to? On 29/12/2012, at 11:34 AM, Sam Raker wrote: > Hello, > I've got a very tight deadline, and I'm encountering a very frustrating > problem. Every time I try to use loa

loaddata deserializationerror: maximum recursion depth exceeded while calling a Python object

2012-12-29 Thread Sam Raker
Hello, I've got a very tight deadline, and I'm encountering a very frustrating problem. Every time I try to use loaddata to load my data into my database, I get the loaddata error in the subject. I've tried YAML, I've tried JSON, I've tried excerpting only a few lines of each, all to no avail. I