I am using postgresql with postgresql_psycopg2.
On 1 Ağustos, 17:21, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On 8/1/07, omat <[EMAIL PROTECTED]> wrote:
>
>
>
> > Shouldn't Django be reporting that failure? Success messages are
> > confusing.
>
> I _did_ get an error message, warning
On 8/1/07, omat <[EMAIL PROTECTED]> wrote:
>
> Shouldn't Django be reporting that failure? Success messages are
> confusing.
I _did_ get an error message, warning me about an invalid primary key:
psycopg.DatabaseError: {: 'ERROR: insert
or update on table "mytest_documentissue" violates foreign
Yes, the problem was I didn't have the second user on the db that I an
trying to initialize. As I only dump data for one application, and the
user data is in an other application, the foreign key constraint
fails. Thanks a lot...
Shouldn't Django be reporting that failure? Success messages are
co
On 8/1/07, omat <[EMAIL PROTECTED]> wrote:
>
> My bad. In my previous post, I think it would be a good idea to crop
> the models a bit for simplicity. Please use this one:
> http://dpaste.com/hold/15751/
Works fine for me, as long as you have two users defined (pk=1 and
pk=2). The fixture you pro
My bad. In my previous post, I think it would be a good idea to crop
the models a bit for simplicity. Please use this one:
http://dpaste.com/hold/15751/
On 1 Ağustos, 16:31, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On 8/1/07, omat <[EMAIL PROTECTED]> wrote:
>
> > Thanks for the reply
On 8/1/07, omat <[EMAIL PROTECTED]> wrote:
>
> Thanks for the reply Russ...
>
> The models are here:
> http://dpaste.com/hold/15746/
>
> The dump in json format is here:
> http://dpaste.com/hold/15747/
>
Are you sure the fixture comes from these models? I get an immediate
failure because industry
I have custom save methods like:
class Issue(models.Model):
title = models.CharField(maxlength=150)
parent = models.ForeignKey('self',
null = True,
blank = True)
industries = models.ManyToManyField(Industry,
On 8/1/07, David Reynolds <[EMAIL PROTECTED]> wrote:
>
> How about .save() is being overridden and Super(Model, self).save()
> isn't being called?
FYI - as of [5658], fixtures call save() directly on the base Model
class, ignoring any user-defined save method.
Yours,
Russ Magee %-)
--~--~--
Thanks for the reply Russ...
The models are here:
http://dpaste.com/hold/15746/
The dump in json format is here:
http://dpaste.com/hold/15747/
On 1 Ağustos, 15:52, "Russell Keith-Magee" <[EMAIL PROTECTED]>
wrote:
> On 8/1/07, omat <[EMAIL PROTECTED]> wrote:
>
>
>
> > Installed 34 object(s) f
On 1 Aug 2007, at 1:52 pm, Russell Keith-Magee wrote:
On 8/1/07, omat <[EMAIL PROTECTED]> wrote:
Installed 34 object(s) from 1 fixture(s)
If this message is getting printed, then the fixture is getting loaded
_somewhere_, save() has been called on 34 object instances, and the
transaction h
On 8/1/07, omat <[EMAIL PROTECTED]> wrote:
>
> Installed 34 object(s) from 1 fixture(s)
If this message is getting printed, then the fixture is getting loaded
_somewhere_, save() has been called on 34 object instances, and the
transaction has been successfully committed.
The only way I can think
Hi,
It seems easy as 1-2-3 but, I couldn't manage to loaddata in my
fixture back into the db.
Despite the success message at the end, no data is inserted into the
db. I am running django revision 5783 with postgres.
I tried the following for json and xml. Both end with success messages
but with
12 matches
Mail list logo
