Re: loaddata issue

2007-08-26 Thread Drasty
It seems like it was an issue with the transition from MySQL to PostgreSQL; I had been using build 6001 (as I noted at the end, sorry it wasn't very obvious), but I just ran svn update and was able to loaddata, although the project will remain on MySQL. On Aug 26, 9:16 am, "Russell Keith-Magee" <

Re: loaddata issue

2007-08-26 Thread Russell Keith-Magee
On 8/26/07, Drasty <[EMAIL PROTECTED]> wrote: > > Loading 'courses' fixtures... > Installing xml fixture 'courses' from '/../eeyore/courses/fixtures'. > Problem installing fixture '/../eeyore/courses/fixtures/courses.xml': > node is missing the 'name' attribute This sounds like there is an attri

loaddata issue

2007-08-25 Thread Drasty
I'm attempting to use the loaddata action to load an XML file (generated using the dumpdata action on an MySQL db) to populate an app in a project that is using PostgreSQL for its db. I receive the following error: Loading 'courses' fixtures... Installing xml fixture 'courses' from '/../eeyore/co

Re: loaddata issue

2007-05-12 Thread Russell Keith-Magee
On 5/7/07, Mark Jarecki <[EMAIL PROTECTED]> wrote: > > Hi Russ, > > Thank you for all your help, I renamed my app name and it works fine > at the moment. > > I posted a ticket (I hope its ok, my fist one) #4231. Ticket description was fantastic. FYI, I've fixed the problem in [5204]. The problem

Re: loaddata issue

2007-05-06 Thread Mark Jarecki
Hi Russ, Thank you for all your help, I renamed my app name and it works fine at the moment. I posted a ticket (I hope its ok, my fist one) #4231. Thanks again, Mark. On 06/05/2007, at 10:21 AM, Russell Keith-Magee wrote: On 5/5/07, Mark Jarecki <[EMAIL PROTECTED]> wrote: > > > Hi Russ,

Re: loaddata issue

2007-05-05 Thread Russell Keith-Magee
On 5/5/07, Mark Jarecki <[EMAIL PROTECTED]> wrote: > > > Hi Russ, > > Here is the transcript of the output: > > ./manage.py sqlall Guide Ok - found it. The problem is the capitalization on the application name. For some reason, django isn't taking the lower case version of the application name wh

Re: loaddata issue

2007-05-04 Thread Mark Jarecki
Hi Russ, Here is the transcript of the output: ./manage.py sqlall Guide BEGIN; CREATE TABLE "Guide_venuetype" ( "id" serial NOT NULL PRIMARY KEY, "venueTypeName" varchar(200) NOT NULL, "venueTypeSlug" varchar(50) NOT NULL ); CREATE TABLE "Guide_venue" ( "id" serial NOT NULL PRIMARY KEY,

Re: loaddata issue

2007-05-04 Thread Russell Keith-Magee
On 5/4/07, Mark Jarecki <[EMAIL PROTECTED]> wrote: > > Running the latest django vesion, just ran svn. > > Cut down models: .. I loaded some same venuetype data using the admin interface, dropped the db, recreated it, synced and loaded the data; it worked fine for me (Postgres 8.1 on OSX, psycopg

Re: loaddata issue

2007-05-04 Thread Mark Jarecki
Running the latest django vesion, just ran svn. Cut down models: class VenueType(models.Model): venueTypeName = models.CharField(maxlength=200, db_index=True) venueTypeSlug = models.SlugField(prepopulate_from= ('venueTypeName',), db_index=True) class Admin: pass class V

Re: loaddata issue

2007-05-03 Thread Russell Keith-Magee
On 5/4/07, Mark Jarecki <[EMAIL PROTECTED]> wrote: > > Hi, > > I've come across an issue trying to loaddata into my database, and am > wondering if anyone else has come across this too? and how to go about > fixing it. > > I have Apache2.2.4, mod_python3.3.1, Python-2.5.1, postgresql-8.2.4, > psyc

loaddata issue

2007-05-03 Thread Mark Jarecki
Hi, I've come across an issue trying to loaddata into my database, and am wondering if anyone else has come across this too? and how to go about fixing it. I have Apache2.2.4, mod_python3.3.1, Python-2.5.1, postgresql-8.2.4, psycopg2-2.0.5.1 installed. Please let me know if you require any