Re: DB migration: Loading a massive fixture dump

Just for the follow-up, I ended up using pgloader and after some argument tweaking, it worked. Cheers. On Wednesday, September 2, 2020 at 7:26:04 AM UTC+2 Fred Blaise wrote: > Hi Mike, > > Thanks for the answer. > > Yes, I was aware yet hopeful regarding the size. > > Regarding the converter, I

Re: DB migration: Loading a massive fixture dump

Hi Mike, Thanks for the answer. Yes, I was aware yet hopeful regarding the size. Regarding the converter, I would be interested to take a look at your py3 work, if you could forward it along. Thanks. On Wed, Sep 2, 2020, 00:21 Fred Blaise wrote: > Hi, > > I have to migrate a database from m

Re: DB migration: Loading a massive fixture dump

On 2/09/2020 3:51 am, Fred Blaise wrote: > Hi, > > I have to migrate a database from mysql to postgresql. Unfortunately, > there is quite a bit of data in there. > > As a strategy, I thought of using Django's ORM feature, dump the data > from my setup using mysql, and load the fixtures on the other

DB migration: Loading a massive fixture dump

Hi, I have to migrate a database from mysql to postgresql. Unfortunately, there is quite a bit of data in there. As a strategy, I thought of using Django's ORM feature, dump the data from my setup using mysql, and load the fixtures on the other setup using postgresql, such as: # on mysql $ do

Re: DB migration bug in 1.8.3 when creating ManyToMany relation.

Chen, what is the error? is it the same as what i reported here On Tuesday, August 4, 2015 at 4:24:01 AM UTC+4:30, Chen Xu wrote: > > Hi Everyone, > Does anyone experience a bug in 1.8.3 on creating ManyToMany relations? I > have

DB migration bug in 1.8.3 when creating ManyToMany relation.

Hi Everyone, Does anyone experience a bug in 1.8.3 on creating ManyToMany relations? I have the following very simple code: from django.contrib.auth.models import User class Agent(models.Model): name = models.CharField(max_length=100) users = models.ManyToManyField(User, related_name='a

could someone please help me with the following SO doubt on creating a db migration with south - http://stackoverflow.com/questions/18320225/migrating-an-existing-app-via-south Thansks!

-- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. V

Re: Db migration

On Mon, 2009-10-26 at 16:09 +0530, aju mathew wrote: > Hi > > How can I populate values from a python file to database. > > Is it any commands their for db migration from command prompt. > > -- > Thanks & Regards, > Aju P Mathew > http://docs.djangopro

Re: Db migration

On Oct 26, 10:39 am, aju mathew wrote: > Hi > > How can I populate values from a python file to database. > > Is it any commands their for db migration from command prompt. > > -- > Thanks & Regards, > Aju P Mathew What do you mean a 'Python file'?

Db migration

Hi How can I populate values from a python file to database. Is it any commands their for db migration from command prompt. -- Thanks & Regards, Aju P Mathew --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Gr

Re: dumpdata and loaddata as simple DB migration tool?

On Thu, Jun 4, 2009 at 11:19 AM, Brian May wrote: > > On Thu, Jun 04, 2009 at 10:27:35AM +0800, Russell Keith-Magee wrote: >> If you're going to start throwing around claims that loaddata/dumpdata >> doesn't work, you _really_ need to back them up with a demonstrated >> example that proves your c

Re: dumpdata and loaddata as simple DB migration tool?

On Thu, Jun 04, 2009 at 10:27:35AM +0800, Russell Keith-Magee wrote: > If you're going to start throwing around claims that loaddata/dumpdata > doesn't work, you _really_ need to back them up with a demonstrated > example that proves your claim. We provide Trac for precisely this > reason, and you

Re: dumpdata and loaddata as simple DB migration tool?

On Thu, Jun 4, 2009 at 10:00 AM, Brian May wrote: > > On Tue, Jun 02, 2009 at 09:06:38PM -0700, Kegan wrote: >> 1. Use Django's management command "dumpdata" to get the JSON >> representative of an app. Save the JSON into a file (oldmodel.json). >> 2. Git pull the latest code. And do a reset to t

Re: dumpdata and loaddata as simple DB migration tool?

On Tue, Jun 02, 2009 at 09:06:38PM -0700, Kegan wrote: > 1. Use Django's management command "dumpdata" to get the JSON > representative of an app. Save the JSON into a file (oldmodel.json). > 2. Git pull the latest code. And do a reset to the app. So the > database will have the new model schema n

Re: dumpdata and loaddata as simple DB migration tool?

On Wed, Jun 3, 2009 at 11:38 PM, Kegan Gan wrote: > > Hi Russell, > > On the first issue: Good point. I have not the opportunity to work > with such a huge database. > > On the second issue: Yes, what I am doing now is really about writing > conversion code to fit the old json to match the new sc

Re: dumpdata and loaddata as simple DB migration tool?

Hi Russell, On the first issue: Good point. I have not the opportunity to work with such a huge database. On the second issue: Yes, what I am doing now is really about writing conversion code to fit the old json to match the new schema. I find this to be quite straight forward for my use cases,

Re: dumpdata and loaddata as simple DB migration tool?

On Wed, Jun 3, 2009 at 12:06 PM, Kegan wrote: > > Hi, > > About Django database migration. I know there's a couple of tools > available (South, evolution, dmigration, etc), but I am pondering an > alternative here. Hope good discussion entails. > > This is what I am doing manually now for my data

dumpdata and loaddata as simple DB migration tool?

Hi, About Django database migration. I know there's a couple of tools available (South, evolution, dmigration, etc), but I am pondering an alternative here. Hope good discussion entails. This is what I am doing manually now for my database migration needs. 1. Use Django's management command "du

Re: DB migration from Oracle to MySQL

Thank you for your answer Ian. Then I dropped the models for which there is no id (in fact I don't need them). I also removed these apps to prevent dumpdata from trying to read the related tables (which does not exists in the source Oracle DB): 'django.contrib.auth', 'django.contrib.cont

Re: DB migration from Oracle to MySQL

On Apr 3, 11:20 am, olive <[EMAIL PROTECTED]> wrote: > Hello again, > > I've tried dumpdata after having copied back my tweaked models.py to > the Oracle powered Django project. > > After 1 minute of intensive CPU activity this message appears: > > D:\test>python manage.py dumpdata test > Tracebac

Re: DB migration from Oracle to MySQL

Hello again, I've tried dumpdata after having copied back my tweaked models.py to the Oracle powered Django project. After 1 minute of intensive CPU activity this message appears: D:\test>python manage.py dumpdata test Traceback (most recent call last): File "manage.py", line 11, in exec

DB migration from Oracle to MySQL

Hello, I need to migrate a DB schema and data from Oracle to MySQL. How would perform that : 1) Using Oracle SqlDevelopper migration tool ? 2) Using MySql migration tool ? 3) Using inspectdb/syncdb ? 4) ? I've already tried inspectdb/syncdb with some apparent success by tw

Re: An idea on DB migration

On 7/6/07, SmileyChris <[EMAIL PROTECTED]> wrote: > > If you haven't already, check out http://www.aswmc.com/dbmigration/ > > It's quite a good solution for migration. > I've been writing a wrapper on top of that to handle auto-migration, > which I'm mostly happy with. Just have to tie some loose

Re: An idea on DB migration

If you haven't already, check out http://www.aswmc.com/dbmigration/ It's quite a good solution for migration. I've been writing a wrapper on top of that to handle auto-migration, which I'm mostly happy with. Just have to tie some loose ends and I'll put it up somewhere to share. --~--~-

Re: An idea on DB migration

On 7/4/07, Carl Karsten <[EMAIL PROTECTED]> wrote: > > The problem I see is maintaining the generated file. This process will often > start before the target system is stable, so as soon as you start making > changes > to the target model, the converter will need to be updated too. If the > tra

Re: An idea on DB migration

Noam Raphael wrote: > On 7/4/07, Carl Karsten <[EMAIL PROTECTED]> wrote: >> I don't like the "edit the file" part. I can think of 2 alternatives: >> >> 1. add an attribute to one/both of the models. something like >> >> class Book(models.Model): >> name = models.CharField(blank=True, "migra

Re: An idea on DB migration

On 7/4/07, nick feng <[EMAIL PROTECTED]> wrote: > The django has already provided the way to use SQL, I don't think this is > needed. Well, I'm not a SQL expert, and I don't feel comfortable with adding fields manually. I'm never sure whether my SQL statement is what Django would have issued whe

Re: An idea on DB migration

On 7/4/07, Carl Karsten <[EMAIL PROTECTED]> wrote: > > I don't like the "edit the file" part. I can think of 2 alternatives: > > 1. add an attribute to one/both of the models. something like > > class Book(models.Model): > name = models.CharField(blank=True, "migrate_to"="book_name" ) > > 2

Re: An idea on DB migration

The django has already provided the way to use SQL, I don't think this is needed. - Original Message - From: "Noam" <[EMAIL PROTECTED]> To: "Django users" Sent: Thursday, July 05, 2007 2:40 AM Subject: An idea on DB migration > > > Hello, >

Re: An idea on DB migration

Noam wrote: > For example, say that I have a directory with the old site (and old > models) and a directory with the new site. The only difference between > them is that I renamed the field store.Book.name to > store.Book.book_name. I will run "django-admin.py migrate oldsitedir > newsitedir". Th

An idea on DB migration

Hello, I have an idea on how DB migration can work in Django. It's very simple, it will allow the programmer to do anything he wants in the migration, and he will have to learn almost nothing in order to migrate the DB. The drawback is that it's not very efficient, which means th