Re: Python Database Migration Tool

I believe that you will have to translate your postgres db to a mssql schema, perform the mapping by yourself, and elaborate a series of procedures to get this done. As far as I know, no tool will cover all of your needs. Em qui., 29 de fev. de 2024 às 12:01, sebasti...@gmail.com < sebastian.ju...

Re: Python Database Migration Tool

On Thu, 29 Feb 2024 at 15:01, sebasti...@gmail.com < sebastian.ju...@gmail.com> wrote: > Hey, > > i have 2 different database systems. In source postgresql and target MS > SQL. Now i have on source DBMS a database with a complete different schema > like in target DBMS. Now i search a solution wher

Python Database Migration Tool

Hey, i have 2 different database systems. In source postgresql and target MS SQL. Now i have on source DBMS a database with a complete different schema like in target DBMS. Now i search a solution where i can connect to different DBMS Systems and can make a mapping between different source tab

Re: Heroku database migration

Tried sending you that ss :) On Mon, Jul 20, 2020 at 10:15 PM John McClain wrote: > why not commit to git and run deploy within heroku console as we have > always done? > > On Sun, 19 Jul 2020 at 17:47, Aman Mandloi > wrote: > >> Added a small model 'new_model' in existing app 'existing_app' on

Re: Heroku database migration

why not commit to git and run deploy within heroku console as we have always done? On Sun, 19 Jul 2020 at 17:47, Aman Mandloi wrote: > Added a small model 'new_model' in existing app 'existing_app' on Django, > Entered commands manage.py makemigrations and manage.py migrate it > migrated changes

Re: Heroku database migration

I've experienced this problem many times and the solution is to simply change the name of the model then do the migration and after that you can change the model name to the original name and run the migration again, I think it's a bug in django. On Sun, Jul 19, 2020 at 8:47 PM Heet Gupta wrote:

Re: Heroku database migration

Firstly push your code containing the migrations folder to heroku ("git push heroku master"), then follow the below steps - In your terminal run the command "heroku run bash". It will open the heroku terminal for you. Now In the heroku terminal run "python manage.py migrate" On Sunday, July 19,

Re: Heroku database migration

bash% heroku run python. /manage.py migrate søn. 19. jul. 2020, 18:48 skrev Aman Mandloi : > Added a small model 'new_model' in existing app 'existing_app' on Django, > Entered commands manage.py makemigrations and manage.py migrate it > migrated changes to local database. > Tried to apply same o

Re: Database migration issue

Ok, I figure it out, When application configuration class is used in INSTALLED_APPS, the name field of AppConfig subclass should be the path of that application. AppConfig.name¶ > > Full > Python path to the applic

Re: Database migration issue

> > When I just change the api.blogs.apps.BlogsConfig to api.blogs , it > worked fine. I am curious why api.blogs.apps.BlogsConfig doesn't work > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop rec

Database migration issue

Hi, everyone. I'm completely new to DRF and I structured my first project as the following. When I run *python manage.py makemigrations * script, it gives errors. I guess it's related to my folder structure but don't know exactly what's wrong with it. [image: Capture.PNG] Any help would be

Re: database migration

Hallöchen! Torsten Bronger writes: > Hallöchen! > > Michael P. Soulier writes: > >> On 29/12/10 Torsten Bronger said: >> >>> I don't recommend that. If the database exceeds a certain size >>> (and "certain" is MBs, not GBs), this simply fails. >> >> Is there a bug report for this issue? I find t

Re: database migration

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 30/12/10 13:17, Torsten Bronger wrote: >> Is there a bug report for this issue? I find that very >> > disappointing. > http://1.2.3.12/bmi/stc.celeb.gate.cc/banner/pi/0120.gif What i found disappointing is sending a NSFW image to a django list wi

Re: database migration

Hallöchen! Michael P. Soulier writes: > On 29/12/10 Torsten Bronger said: > >> I don't recommend that. If the database exceeds a certain size >> (and "certain" is MBs, not GBs), this simply fails. > > Is there a bug report for this issue? I find that very > disappointing. http://1.2.3.12/bmi/st

Re: database migration

On 29/12/10 Emmanuel Mayssat said: > I was looking at a possibility of using manage.py dumpscript and > manage.py runscript > from django-extensions. But it is not straight forward either. dumpdata/loaddata is quite simple, I recently used it myself. Torsten suggested that there's a problem using

Re: database migration

On 29/12/10 Torsten Bronger said: > I don't recommend that. If the database exceeds a certain size (and > "certain" is MBs, not GBs), this simply fails. Is there a bug report for this issue? I find that very disappointing. Mike -- Michael P. Soulier "Any intelligent fool can make things bigge

Re: database migration

Michael, that's encouraging ;-) I was looking at a possibility of using manage.py dumpscript and manage.py runscript from django-extensions. But it is not straight forward either. Wasn't django supposed to be database agnostic? Now, I understand what they really meant. Pick you database carefully

Re: database migration

Hallöchen! Michael P. Soulier writes: > On 28/12/10 Emmanuel Mayssat said: > >> I have a classic database dump question >> >> I would like to migrate from sqlite to mysql. >> How can I dump and import the data? > > See the manage.py dumpdata/loaddata commands. I don't recommend that. If th

Re: database migration

within the main project directory in linux python manage.py dumpdata > data.json command will dump your data to a json file change settings.py to use mysql, after that python manage.py syncdb this will create tables followed by python manage.py loaddata data.json will load everything back

Re: database migration

see if this url could help you: http://www.maxkpage.com/blog/free-sqlite-to-mysql-converter-super-easy/ On Dec 29, 7:37 am, Emmanuel Mayssat wrote: > I have a classic database dump question > > I would like to migrate from sqlite to mysql. > How can I dump and import the data? > Regards, > -

Re: database migration

On 28/12/10 Emmanuel Mayssat said: > I have a classic database dump question > > I would like to migrate from sqlite to mysql. > How can I dump and import the data? See the manage.py dumpdata/loaddata commands. Mike signature.asc Description: Digital signature

database migration

I have a classic database dump question I would like to migrate from sqlite to mysql. How can I dump and import the data? Regards, -- E -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@google

Re: Problem with contrib.auth in database migration

On Apr 2, 12:51 pm, dadapapa wrote: > I managed to solve the problem. The solution is to explicitly state > the applications (models) that you want to migrate, and leave out > those that get initialized automatically when doing syncdb > (contenttypes). Here's how it worked for me: > > production s

Re: Problem with contrib.auth in database migration

I managed to solve the problem. The solution is to explicitly state the applications (models) that you want to migrate, and leave out those that get initialized automatically when doing syncdb (contenttypes). Here's how it worked for me: production server: $ python manage.py dumpdata auth custom_a

Problem with contrib.auth in database migration

Dear list, I am using Django 1.0 + MySQL on the production server and Django 1.1 + sqlite3 on my (local) development server. My application uses contrib.auth.User etc. and I am running into the following issue when trying to migrate the production database to the development server. production se

Re: Database Migration Question

Russ - We had a few back and forths about this several weeks ago, if you recall. I now am much better versed in Django and so maybe a bit more capable of making intelligent comments. It would seem to me that with the primitives that I am seeking (which is basically a continuation of hiding the S

Re: Database Migration Question

On Tue, May 6, 2008 at 11:57 AM, jack <[EMAIL PROTECTED]> wrote: > > Are there any Python/Django methods that represent generic database > commands such as creating a new table, renaming or dropping a column, > etc.? My thinking is that if these generic methods existed, so that > all I needed

Database Migration Question

Are there any Python/Django methods that represent generic database commands such as creating a new table, renaming or dropping a column, etc.? My thinking is that if these generic methods existed, so that all I needed to do was specifiy the correct info abt my DBMS in the Settings file, I could

Re: revert database migration

Thank you... for the help I started using the django evolution its fine... On Mar 4, 3:24 am, "Ramiro Morales" <[EMAIL PROTECTED]> wrote: > On Tue, Mar 4, 2008 at 2:58 AM, stranger <[EMAIL PROTECTED]> wrote: > > After searching this group archive i didnot find much regarding my question >

Re: revert database migration

On Tue, Mar 4, 2008 at 2:58 AM, stranger <[EMAIL PROTECTED]> wrote: > After searching this group archive i didnot find much regarding my question Really? http://groups.google.com/group/django-users/search?hl=en&q=migrations&start=0&scoring=d&hl=en&; There is a difference between searching the a

Re: revert database migration

Ok thank you found the answer. "Django will look for any new models that have been defined, and add a database table to represent those new models." So how about the django evolution. Is it fine to use it to track changes in django models and make database migrations. It is very sad that django d

Re: revert database migration

Hi James, I have been following you blog for a very long time. Good posts. Awaiting you django projects book t... After searching this group archive i didnot find much regarding my question? I think django should automatically make the changes in the model. I have added a new model p

Re: revert database migration

On Sun, Mar 2, 2008 at 11:45 PM, stranger <[EMAIL PROTECTED]> wrote: > Is there a way in django where we can migrate the changes in model, > or revert back database changes to the original(fresh). You probably want to search the archive of this list, which is publicly available and powered by

revert database migration

Hello group, I have a quick question. I have a django project where I have model. I 'syncdb' the database with the model. After that I again added few attributes to the model. but when I apply the syncdb command its not syncing with the database. Is there a way in django where we can m

Re: ANN: DMigrate - A Django Database Migration Tool

On 7/18/07, Ben Ford <[EMAIL PROTECTED]> wrote: > Just out of interest have you explored using SQLAlchemy directly with the > django model..? I mean mapping the SA Table onto the django Model..? I had a > play with that a while back and it seems a very straightforward way of > achieving SA - dj

Re: ANN: DMigrate - A Django Database Migration Tool

Just out of interest have you explored using SQLAlchemy directly with the django model..? I mean mapping the SA Table onto the django Model..? I had a play with that a while back and it seems a very straightforward way of achieving SA - django integration... Ben On 18/07/07, Noam <[EMAIL PROTECTED

Re: ANN: DMigrate - A Django Database Migration Tool

On Jul 18, 4:47 am, "Ben Ford" <[EMAIL PROTECTED]> wrote: > > I haven't looked at the code, but I wonder about the dependency on > > multiple ORMs; the Django ORM cannot expose its own functionality on > > multiple databases at once... > > It can using the multiple-db-support branch (see ticket 47

Re: ANN: DMigrate - A Django Database Migration Tool

Thanks for your comment! Relying on another ORM isn't technically necessary, but it seems to me the easiest way - instead of issuing select statements, the generated code looks like this: for s in src.myapp.City.select(): d = dst.myapp.City() d.id = s.id d.name = s.na

Re: ANN: DMigrate - A Django Database Migration Tool

> I haven't looked at the code, but I wonder about the dependency on > multiple ORMs; the Django ORM cannot expose its own functionality on > multiple databases at once... It can using the multiple-db-support branch (see ticket 4747 for a patch bringing the branch up to date)... There's also a si

Re: ANN: DMigrate - A Django Database Migration Tool

On 7/17/07, Noam Raphael <[EMAIL PROTECTED]> wrote: > I would really like to hear what you think about it (especially if > it's good things...) Tell me! I haven't looked at the code, but I wonder about the dependency on multiple ORMs; the Django ORM cannot expose its own functionality on multiple

ANN: DMigrate - A Django Database Migration Tool

Hello, I'm happy to let you know about DMigrate. DMigrate is a simple tool which lets you migrate Django databases easily. With DMigrate: * You don't have to use any SQL. * You don't need to learn any command for changing database structure. * You can do whatever transformations you like. * Y

Re: Database migration

Thanks... I think I can handle that. If not, I can always roll it back. On Mar 26, 6:36 pm, "Honza Král" <[EMAIL PROTECTED]> wrote: > On 3/27/07, Jonas Maurus <[EMAIL PROTECTED]> wrote: > > > > > > > On Mar 26, 11:10 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > wrote: > > > I apologize for the

Re: Database migration

On 3/27/07, Jonas Maurus <[EMAIL PROTECTED]> wrote: > > On Mar 26, 11:10 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > I apologize for the vague newbie question, but I'm gonna ask it > > anyway... > > > > I'd like to switch DBs from mysql to postgres... how does one do so? I > > assume o

Re: Database migration

On Mar 26, 11:10 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > I apologize for the vague newbie question, but I'm gonna ask it > anyway... > > I'd like to switch DBs from mysql to postgres... how does one do so? I > assume one must export from mysql, import to postgres, then make the > appr

Database migration

I apologize for the vague newbie question, but I'm gonna ask it anyway... I'd like to switch DBs from mysql to postgres... how does one do so? I assume one must export from mysql, import to postgres, then make the appropriate changes in settings.py, but are there any gotchas I should be aware of?

Re: Database Migration

One of my django apps contains testing data about every item our company has manufactured over the last year or so. The database has over 50 million rows of data. Despite this I have successfully migrated the database several times. Sometimes it is trivial. Back up the data for safety and then jus

Re: Database Migration

On 8/25/06, Dave <[EMAIL PROTECTED]> wrote: > > I create my models in models.py, and everything looks great. I launch > the application and millions upon millions of peope start using my app > and creating their own little entries in my database, via the perfect > models.py I wrote. > > But then,

Database Migration

I create my models in models.py, and everything looks great. I launch the application and millions upon millions of peope start using my app and creating their own little entries in my database, via the perfect models.py I wrote. But then, the EVIL CLIENT comes along and requests a change to exis