On 5/31/07, Michal <[EMAIL PROTECTED]> wrote:
>
> I trust to my data, so I temporary disabled save() overriding. Now
> loaddata was successfull, and my application on computer2 works like charm.
Good to hear. I've opened ticket #4459 to address the problem; I've
got some ideas on how to fix the i
> to migrate i do this:
> 1. all code is anyway on svn, so i do a checkout in the new machine
> 2. i do a pg_dump on the old machine, and after setting up the
> database run:
> psql -f dumpfile newdatabase
Unfortunately, I have different versions of PostgreSQL database on my
local enviroment a
> Are you overriding save() in any of your models (in particular,
> anything querying StaticPage model?
Yes, I am. I have there some check code, which prevent to save object,
which will refer to itself.
> The only workaround I know of for this is to do your dump in stages,
> so that the data req
On 31-May-07, at 1:39 PM, Michal wrote:
> I would like migrate data from my Django project on notebook
> (computer1)
> to another machine (computer2). To perform this, I follow this steps:
to migrate i do this:
1. all code is anyway on svn, so i do a checkout in the new machine
2. i do a pg_d
On 5/31/07, Michal <[EMAIL PROTECTED]> wrote:
>
> Hello,
> I would like migrate data from my Django project on notebook (computer1)
> to another machine (computer2). To perform this, I follow this steps:
> ...
> Is this approach correct?
Looks correct to me.
> I ask you for this, because I have
Hello,
I would like migrate data from my Django project on notebook (computer1)
to another machine (computer2). To perform this, I follow this steps:
1) On computer1 I call ./manage.py dumpdata > all.json
2) On computer2 I setup exactly same version of my Django project. Next
I call ./manage.py
6 matches
Mail list logo
