Just to close the loop, I needed to delete all entries whose "model" was
"contenttypes.contenttype" or "scmtools.tool".  Then it worked like a
charm!  Thanks for pointing me ad dumpdata/loaddata, *way* easier than what
I was trying to do with the database manually!

Ian

On Mon, Oct 31, 2011 at 3:50 PM, Mail Team <email....@gmail.com> wrote:

> Oh, I needed to add ".json" to the end of the filename, doh!  But now I'm
> getting this one.
>
> IntegrityError: duplicate key value violates unique constraint
> "django_content_type_app_label_model_key"
> DETAIL:  Key (app_label, model)=(changedescs, change description) already
> exists.
>
> Ian
>
>
> On Sat, Oct 29, 2011 at 9:09 PM, Mail Team <email....@gmail.com> wrote:
>
>> I did the dump like this which seemed to go fine.
>> sudo rb-site manage /path/to/site dumpdata > /another/path/rbdump
>>
>> But when I try to load it, nothing happens.
>> sudo rb-site manage /path/to/new/site loaddata /another/path/rbdump
>> No fixtures found.
>>
>> Does that mean anything to you?
>>
>> Ian
>>
>>
>> On Mon, Sep 26, 2011 at 11:26 AM, Mark <m...@catley.net.nz> wrote:
>>
>>> I recently migrated our SQLite RB database to PostgreSQL. You probably
>>> have two options, first you could use rb-site manage . dumpdata
>>> however that didn't work for me (I think it was because our database
>>> was too big). I ended up having to create a new reviewboard instance,
>>> delete all the records out of all of the tables, then export my mysql
>>> data as csv files (one table at a time) and import it (using the copy
>>> command) into Postgres. It was a pain in the ass because you have to
>>> be very specific about the order which you import tables in order to
>>> satisfy foreign key constraints, but in the end, once I had discovered
>>> the process, only took an hour or two and worked like a charm. I also
>>> had to reset all postgres' sequences (found here wiki.postgresql.org/
>>> wiki/Fixing_Sequences <http://wiki.postgresql.org/wiki/Fixing_Sequences>
>>> ).
>>>
>>> In fear of starting a flame war ... good on ya for changing, Postgres
>>> has much better speed vs reliability tradeoff by default. You get a
>>> lot of stuff for free that would require a guru to get right in MySQL.
>>> I find that, other than experts, people who pick postgres generally
>>> have a good technical reason, whereas those who pick MySQL are merely
>>> chasing brand name.
>>>
>>> On Sep 26, 5:06 pm, Mail Team <email....@gmail.com> wrote:
>>> > I'm running a Review Board server on Mac OS X Server 10.6 that has
>>> MySQL
>>> > built in.  I'm planning on moving it to a 10.7 Server that only has
>>> > PostgreSQL built in.  Is it reasonable to try to migrate my database
>>> from
>>> > MySQL to PostgreSQL and then just recreate the Review Board site on
>>> the 10.7
>>> > Server?
>>>
>>> --
>>> Want to help the Review Board project? Donate today at
>>> http://www.reviewboard.org/donate/
>>> Happy user? Let us know at http://www.reviewboard.org/users/
>>> -~----------~----~----~----~------~----~------~--~---
>>> To unsubscribe from this group, send email to
>>> reviewboard+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/reviewboard?hl=en
>>>
>>
>>
>

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Reply via email to