Re: DJANGO Migrations from older version : South db

cd_import File "", line 969, in _find_and_load File "", line 958, in _find_and_load_unlocked File "", line 673, in _load_unlocked File "", line 665, in exec_module File "", line 222, in _call_with_frames_removed File "/home/ankush/catm

Re: DJANGO Migrations from older version : South db

If you have the original models.py files just run "python manage.py makemigrations" and then "python manage.py migrate". On Wednesday, 02 May, 2018 05:11 PM, Ank wrote: Dear All, I would like to do some migrations that are compatible with older django version using southdb to the newer versi

DJANGO Migrations from older version : South db

Dear All, I would like to do some migrations that are compatible with older django version using southdb to the newer version. How can these files be updated.iḿ attaching one of the file that is needed to be migrated. Any help will be appreciated Best Ank -- You received this message b

Re: ImportError: No module named south

ine > 90, in create > module = import_module(entry) > File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module > __import__(name) > ImportError: No module named south > > -- > You received this message because you are subscribed to th

ImportError: No module named south

", line 90, in create module = import_module(entry) File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module __import__(name) ImportError: No module named south -- You received this message because you are subscribed to the Google Groups "Django use

Re: Error: ImportError: No module named south

On Sunday, August 11, 2013 at 5:00:54 PM UTC+5:30, alekto.a...@gmail.com wrote: > > Hi, > am using django==1.5.1 and south==0.8.2, as well as pip-1.1-py2.7.egg > (python 2.7) > I keep getting this error: ImportError: No module named south, when I run: > sudo python manage.p

Re: south migration: renaming foreign key and m2m tables

would do it slightly differently: 1. create the new table 2. fill the new table (for example with that INSERT INTO ... SELECT I mentioned above) while keeping all primary key values the same 3. drop existing FOREIGN KEY constraints referencing the old table 4. drop the old tables 5. rename t

Re: south migration: renaming foreign key and m2m tables

HI Michal If you are using South, that would mean you're using a version of > Django that's oldee than 1.7, which means you are using a version > that hasn't received security updates for more than a year. Not good. > > Second, South itself has been deprecated

Re: south migration: renaming foreign key and m2m tables

On Thu, May 12, 2016 at 11:46:35PM -0700, schaf...@gmail.com wrote: > HI All, > I'm new in south and I'm wondering how I can merge two models into one. Hi Marcel, If you are using South, that would mean you're using a version of Django that's oldee than 1.7, which mea

south migration: renaming foreign key and m2m tables

HI All, I'm new in south and I'm wondering how I can merge two models into one. I have a model book which derives from the model media. So book has a media_id_ptr (which is already a pk). No I would like to merge all attributes from media into book and get rid of media. I was

south schemamigration merge two tables into one

Hi All, this is my first schemamigration and it is done on Django 1.6 with south. I have a model class 'book' which derives from 'media' and extends it. Now I decided that this splitting is not needed. Therefore I decided to merge the data from 'media' into 'b

Ideas for easier migration from South to Django 1.7+

Hi everyone I'm looking for a way to do a semi-automatic migration of databases from Django 1.6 with South to Django 1.7+ migrations. We have thousands of sites, each using many re-usable apps with many migrations. I'm looking for a way to make this transition as painless as poss

Re: Using South in Django 1.7+

Hi Remco, On 10/08/2015 04:26 AM, Remco Gerlich wrote: [snip] > Can South run on Django 1.7+ at all? Nope. At least not last I tried, and I don't think anyone has done anything on it since. It looked like it would need some major updating, since South integrates closely with the

Using South in Django 1.7+

I want to run South migrations in a Django 1.7+ installation. I know that's now how it's usually done, but we have a special needs use case. Our users have SQLite files that model their project; the SQL schema used has changed over time, and users are on many different versions. Our a

Re: Issues Upgrading to django 1.8 and migrating from south

Hi Tim, many thanks for your help. That, indeed was the issue. Doing a hard upgrade solved it. Cheers! Marcela -- 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

Re: Issues Upgrading to django 1.8 and migrating from south

om django 1.5 + south to 1.8. I am having some > issues when faking migrations with the recommended procedure here > > https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south > > I am using postgres with postgis extension

Issues Upgrading to django 1.8 and migrating from south

Hi all, I am upgrading an app from django 1.5 + south to 1.8. I am having some issues when faking migrations with the recommended procedure here https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south I am using postgres with postgis extension and engine 'E

Re: upgrading from Django 1.6 and south to Django 1.8

upgrading from Django 1.6 and south to Django 1.8. Following the instructions at: https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south seems to work initially but then realize that the user model wasn't updated: https://github.com/django/django/tree/1.8/django/con

Re: moving from Django 1.6 and south to Django 1.8 -- auth migrations not applied

email address', >> blank=True), >> ), >> >> On Monday, April 20, 2015 at 4:19:56 PM UTC-4, Scott Hostovich wrote: >>> >>> I moving from Django 1.6 and south to Django 1.8. I followed the >>> instructions at >>> https://docs.django

Re: moving from Django 1.6 and south to Django 1.8 -- auth migrations not applied

d( > model_name='user', > name='email', > field=models.EmailField(max_length=254, verbose_name='email address', > blank=True), > ), > > On Monday, April 20, 2015 at 4:19:56 PM UTC-4, Scott Hostovich wrote: >> >> I movi

Re: moving from Django 1.6 and south to Django 1.8 -- auth migrations not applied

), On Monday, April 20, 2015 at 4:19:56 PM UTC-4, Scott Hostovich wrote: > > I moving from Django 1.6 and south to Django 1.8. I followed the > instructions at > https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south > and things seemed to work fine. Then

upgrading from Django 1.6 and south to Django 1.8

I'm upgrading from Django 1.6 and south to Django 1.8. Following the instructions at: https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south seems to work initially but then realize that the user model wasn't updated: https://github.com/django/django/tree/

moving from Django 1.6 and south to Django 1.8 -- auth migrations not applied

I moving from Django 1.6 and south to Django 1.8. I followed the instructions at https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south and things seemed to work fine. Then I noticed that the auth migrations did not get applied to the database (https://github.com

Re: Installing south and using sqlite3's :memory: ruins total test suite time

It seems, for some reason settings.COMPRESS_ENABLED gets set to False when south is installed. On Tuesday, January 20, 2015 at 12:37:44 PM UTC-8, Peter Bengtsson wrote: > > I have a django project on django 1.6. It's using django-nose and it's > using sqlite3's :memo

Re: Installing south and using sqlite3's :memory: ruins total test suite time

Quick update there, I've figured out where the time is spent. Those ~45 seconds is caused by django_compressor calling out to `lessc` to convert .less files to .css. I'm now trying to figure out why having south in INSTALLED_APPS changes whether that gets run or not. It shouldn'

Installing south and using sqlite3's :memory: ruins total test suite time

I have a django project on django 1.6. It's using django-nose and it's using sqlite3's :memory: trick: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': ':memory:', } } Before I

Re: django 1.7 migrations upgrade from south: db.delete_foreign_key replacement?

ement at the db level and try to emulate what the db can do natively and much quicker Nicola > /Markus > > On Friday, November 14, 2014 4:23:52 PM UTC+1, drakkan wrote: >> >> Hi, >> >> I'm migrating my app to 1.7 and to builtin django migrations from south, &

Re: django 1.7 migrations upgrade from south: db.delete_foreign_key replacement?

suggest you go with a "RunSQL" operation where you drop the constraint: https://docs.djangoproject.com/en/1.7/ref/migration-operations/#django.db.migrations.operations.RunSQL /Markus On Friday, November 14, 2014 4:23:52 PM UTC+1, drakkan wrote: > > Hi, > > I'm migrating

django 1.7 migrations upgrade from south: db.delete_foreign_key replacement?

Hi, I'm migrating my app to 1.7 and to builtin django migrations from south, I need something like this: http://south.readthedocs.org/en/latest/databaseapi.html#db-delete-foreign-key how to remove a foreign key using django builtin migration api? Please note that my purpose is to remov

Problems with removing South after upgrading to 1.7

Not sure if this is a bug , so I'll report it here. After upgrading to Django 1.7 and running all the migrations, I removed South from the installed apps. This led to to this error popping up on every migration: duplicate key value violates unique const

Re: Migrating to a custom User model with South

? >>>>>>> >>>>>>> >>>>>>> 2014-09-01 8:17 GMT+01:00 Guy Tamir : >>>>>>> >>>>>>>> Hey all, >>>>>>>> >>>>>>>> I'm trying to create a custom

Re: Migrating to a custom User model with South

;>> <http://www.caktusgroup.com/blog/2013/08/07/migrating-custom-user-model-django/>, >>>>>>> I created the new model, ran a "schemamigration" once, which >>>>>>> created the tables in the DB, >>>>>

Re: Migrating to a custom User model with South

which >>>>>> created the tables in the DB, >>>>>> also ran the "Migrate" command once with the copying code in the >>>>>> "forward" method (like instructed in the tutorial in bullet no. 10. >>>>>> >>>

Re: Migrating to a custom User model with South

and once with the copying code in the >>>>> "forward" method (like instructed in the tutorial in bullet no. 10. >>>>> >>>>> The new custom model table was created and all the previous users were >>>>> copied

Re: Migrating to a custom User model with South

DB, >>>> also ran the "Migrate" command once with the copying code in the >>>> "forward" method (like instructed in the tutorial in bullet no. 10. >>>> >>>> The new custom model table was created and all the previous users were >>>

Re: Migrating to a custom User model with South

g code in the >>> "forward" method (like instructed in the tutorial in bullet no. 10. >>> >>> The new custom model table was created and all the previous users were >>> copied correctly. >>> Now, I'm trying to change the "AUTH_USER_MOD

Re: Migrating to a custom User model with South

del, but when I run the migrate command I'm getting >> this error: >> ImproperlyConfigured: AUTH_USER_MODEL refers to model >> 'myappname.CustomUser' that has not been installed >> >> I'm new to South, and this is my first time trying to work wit

Re: Migrating to a custom User model with South

his error: > ImproperlyConfigured: AUTH_USER_MODEL refers to model > 'myappname.CustomUser' that has not been installed > > I'm new to South, and this is my first time trying to work with the custom > User option.. > Not really sure how to fix this.. > > So

Migrating to a custom User model with South

quot;AUTH_USER_MODEL" to newly created custom User model, but when I run the migrate command I'm getting this error: ImproperlyConfigured: AUTH_USER_MODEL refers to model 'myappname.CustomUser' that has not been installed I'm new to South, and this is my first time t

Re: django - south :Getting error with migration

Hi Ram Yep, South supports MySQL - it's that MySQL doesn't support schema-altering statements in transactions. The problem is clearly stated - you are trying to make a field unique despite the data in that field *not* being unique. In particular, it looks like you have two entries

django - south :Getting error with migration

ith: - no dry run output for delete_unique_column() due to dynamic DDL, sorry ! The South developers regret this has happened, and would ! like to gently persuade you to consider a slightly ! easier-to-deal-with DBMS (one that supports DDL transactions) ! NOTE: The error which caused the m

South to Migrations detail

In South, automatically generated migrations that add models fire the function send_create_signal(), which among other things, results in a ContentType record being written for the new model. Except that it doesn't, because it actually just queues up that signal to be fired at the end of

How to reverse both Django South migrations and source code?...

Django Users, I'm having a problem reversing a Django South migration while also reverting my source code to an an older version. Any help? Details: My algorithm for doing a release is essentially: 1. Update the source files 2. % python manage.py migrate --all This works great when m

Strange behavior with Django 1.5.4 and syncbd/South (missing model fields)

Hello, I have a strange problem trying to transform my model fields to PostgreSQL tables. The problem is described here: http://stackoverflow.com/questions/22545252/django-1-5-4-syncdb-not-creating-some-fields-in-postgresql-9-1-postgis-2-tables I don't want to duplicate content, so I just send t

Re: Question About South And Migrating to Production

We have used South for staging and production for a while now (what good otherwise it is?). Our deployment flow is something on the lines of: (Note: Tasks are automated using Fabric) 1. Have a production_settings.py file in the git repo 2. Migrations are also commited to the repo 3. When

Question About South And Migrating to Production

inserted the dump file into the two databases. I can switch the app on the production machine from dev or prod databases easily. My question is what happens when I change the database on the development machine. I can use south to migrate the database with no issues. I can deploy the new version of the

Re: Problems Adding Django South Tool

owing (notice the trailing slash) which did NOT work: $* ./manage.py migrate southtut/* After I entered the command without the trailing slash, it DID work: $* ./manage.py migrate southtut* So, it seems like all the steps to take are the following: 1) install south (for example, *pip install

Re: Duplicate Column name Django south migration Error

` longtext > NULL; [] >- no dry run output for alter_column() due to dynamic DDL, sorry >= ALTER TABLE `vendor_vendorprofile` ADD COLUMN `contact_name_en` > varchar(100) NULL; [] >- no dry run output for alter_column() due to dynamic DDL, sorry >= ALTER TABLE `vend

Duplicate Column name Django south migration Error

rprofile` ADD COLUMN `contact_name_en` varchar(100) NULL; [] - no dry run output for alter_column() due to dynamic DDL, sorry = ALTER TABLE `vendor_subcategory` ADD COLUMN `name_en` varchar(200) NULL; [] - no dry run output for alter_column() due to dynamic DDL, sorry ! The South developers regr

Re: 'python manage.py migrate' command gives error even after installing south

Check the documentation for south and go through the tutorial at http://south.readthedocs.org/en/latest/tutorial/part1.html - you need to do an initial migration, and then an auto migration. Also, the taceback you posted says there is a syntax error in the question model Cheers, Nigel 07914

Re: 'python manage.py migrate' command gives error even after installing south

unknown command' . So i searched for > it and found that its most probably due to 'south' not installed. i checked > it on python shell by giving the command - 'import south' which resulted in > 'unknown module'. So I installed south first by usin

'python manage.py migrate' command gives error even after installing south

I was going through Django tutorials and found the command - 'python manage.py migrate' to give output as 'unknown command' . So i searched for it and found that its most probably due to 'south' not installed. i checked it on python shell by giving the command - &#

South migration when custom field definitions change

I have an app that uses some custom model fields. These are subclasses of standard fields. I have tried to include as many defaults as possible in custom field to stick to DRY. I have written South introspection rules for these that work fine when I change a model What happens when I change

Re: Django South - SyntaxError: invalid syntax (, line 1)

be: self.name = self.name.upper() ? On Monday, September 30, 2013 9:52:09 AM UTC-5, Ivan Goncalves wrote: > > Hi > > I'm having trouble with the South. > > In the model below: > > class Carrier (models.Model): > name = models.CharField (max_length =

Re: Django South - SyntaxError: invalid syntax (, line 1)

<http://about.me/leonardo.giordani> - My GitHub page<https://github.com/lgiordani>- My Coderwall profile <https://coderwall.com/lgiordani> 2013/9/30 Ivan Goncalves > Hi > > I'm having trouble with the South. > > In the model below: > > class Carr

Django South - SyntaxError: invalid syntax (, line 1)

Hi I'm having trouble with the South. In the model below: class Carrier (models.Model): name = models.CharField (max_length = 40, blank = False, null = False, verbose_name = 'Name') user = models.ForeignKey (User, blank = True, null = True) def save (sel

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: South doesn't recognize modification in ManytoMany fields

Hi, On Thu, 15 Aug 2013 03:31:08 +0530 Pradeep Kumar wrote: > I have made a model change from > standard = models.ManyToManyField(Standard) > to > standard = models.ManyToManyField(Standard, blank = True, null = True) > South schemamigration for this app doesn't recognize t

Re: South doesn't recognize modification in ManytoMany fields

On 15/08/2013 8:01am, Pradeep Kumar wrote: I have made a model change from standard = models.ManyToManyField(Standard) to standard = models.ManyToManyField(Standard, blank = True, null = True) South schemamigration for this app doesn't recognize the change ? I think it is probabl

South doesn't recognize modification in ManytoMany fields

I have made a model change from standard = models.ManyToManyField(Standard) to standard = models.ManyToManyField(Standard, blank = True, null = True) South schemamigration for this app doesn't recognize the change ? http://stackoverflow.com/questions/18243039/south-migrating-foriegn-key

Re: south in windows

Thank you! That solved my problem. On Mon, Aug 12, 2013 at 5:05 AM, Mike Dewhirst wrote: > On 12/08/2013 5:36am, Karl Arunachal wrote: > >> Hi, >> I am trying to sync south in my db, but i can't sync it. Its giving me >> an error: >> (use ./manage.py migrate t

Re: Error: ImportError: No module named south

before installing psycopg2 you have to install Postgres, you did it right? To test the south use the sqlite3 first then switch to Postgres Em domingo, 11 de agosto de 2013 08h30min54s UTC-3, alekto.a...@gmail.com escreveu: > > Hi, > am using django==1.5.1 and south==0.8.2, as well a

Re: south in windows

On 12/08/2013 5:36am, Karl Arunachal wrote: Hi, I am trying to sync south in my db, but i can't sync it. Its giving me an error: (use ./manage.py migrate to migrate these) Is there anyway to do this command, "./manage.py", in windows. I could have done it by chmod + x manage.py i

south in windows

Hi, I am trying to sync south in my db, but i can't sync it. Its giving me an error: (use ./manage.py migrate to migrate these) Is there anyway to do this command, "./manage.py", in windows. I could have done it by chmod + x manage.py in other os. But how do i do it in windows? Is

Re: Error: ImportError: No module named south

I manage to solve this problem using this guid: http://www.springmerchant.com/blog/psycopg2-virtualenv-install-pg_config-executable-not-found/ (django_project)alekto@kalahari:~/Web/prosjekt/django_project$ python manage.py validate 0 errors found Thank you for you time. Have a nice day :) --

Re: Error: ImportError: No module named south

/core/management/__init__.py", >>> line 392, in execute >>> self.fetch_command(subcommand).run_from_argv(self.argv) >>> File >>> "/home/alekto/.virtualenv/django_project/local/lib/python2.7/site-packages/django/core/management/__init__.py", >

Re: Error: ImportError: No module named south

/alekto/.virtualenv/django_project/local/lib/python2.7/site-packages/django/core/management/__init__.py", >> line 77, in load_command_class >> module = import_module('%s.management.commands.%s' % (app_name, name)) >> File >> "/home/alekto/.virtuale

Re: Error: ImportError: No module named south

__.py", > line 77, in load_command_class > module = import_module('%s.management.commands.%s' % (app_name, name)) > File > "/home/alekto/.virtualenv/django_project/local/lib/python2.7/site-packages/django/utils/importlib.py", > line 35, in import_module

Re: Error: ImportError: No module named south

home/alekto/.virtualenv/django_project/local/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module __import__(name) File "/home/alekto/.virtualenv/django_project/local/lib/python2.7/site-packages/south/management/commands/__init__.py", line 12, in fro

Re: Error: ImportError: No module named south

so, should I try to install psycopg2 to this project with pip install psycopg2? -- 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...@googleg

Re: Error: ImportError: No module named south

install psycopg2 btw, if you created the virtualenv you should need to sudo On Sun, Aug 11, 2013 at 6:05 PM, Alekto Antarctica < alekto.antarct...@gmail.com> wrote: > (django_project)alekto@kalahari:~/Web/prosjekt/django_project$ pip freeze > Django==1.5.1 > South==0.8.2 &g

Re: Error: ImportError: No module named south

(django_project)alekto@kalahari:~/Web/prosjekt/django_project$ pip freeze Django==1.5.1 South==0.8.2 argparse==1.2.1 distribute==0.6.24 wsgiref==0.1.2 -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this grou

Re: Error: ImportError: No module named south

from this it looks like the error is that you don't have the postgres driver, nothing to do with south On Sun, Aug 11, 2013 at 5:51 PM, wrote: > *So this is what I am getting if I run the python manage.py syncdb, > without sudo:* > > (django_project)alekto@kalaha

Re: Error: ImportError: No module named south

rtError: No module named south > > > > 2013/8/11 Avraham Serour > >> did you active the virtualenv? >> >> >> On Sun, Aug 11, 2013 at 5:34 PM, wrote: >> >>> My python path shows among other >>> paths, >>> /home/alekto/.virt

Re: Error: ImportError: No module named south

env/django_project/local/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module __import__(name) File "/home/alekto/.virtualenv/django_project/local/lib/python2.7/site-packages/south/management/commands/__init__.py", line 12, in from south.hacks i

Re: Error: ImportError: No module named south

Yes, I have already activated the virtualenv project: *(django_project)*alekto@kalahari:~/Web/prosjekt/django_project$ sudo python manage.py syncdb ImportError: No module named south 2013/8/11 Avraham Serour > did you active the virtualenv? > > > On Sun, Aug 11, 2013 at 5:3

Re: Error: ImportError: No module named south

did you active the virtualenv? On Sun, Aug 11, 2013 at 5:34 PM, wrote: > My python path shows among other > paths, > /home/alekto/.virtualenv/django_project/local/lib/python2.7/site-packages/. > When I look into this dir, I find both south and > South-0.8.2-py2.7.egg-info

Re: Error: ImportError: No module named south

My python path shows among other paths, /home/alekto/.virtualenv/django_project/local/lib/python2.7/site-packages/. When I look into this dir, I find both south and South-0.8.2-py2.7.egg-info. -- You received this message because you are subscribed to the Google Groups "Django users&q

Error: ImportError: No module named south

Hi, am using django==1.5.1 and south==0.8.2, as well as pip-1.1-py2.7.egg (python 2.7) I keep getting this error: ImportError: No module named south, when I run: sudo python manage.py syncdb. I have added south as the last line to my INSTALLED_APPS in settings.py. Does anyone here have a

Re: South with MySQL?

; new fields, but if I go into the shell, import the view, and do > DataTable.objects.all() I get "Unknown column 'myapp_datatable.type2stub' in > 'field list'". > So is there a way to resolve this without deleting the database and starting > again with on

Re: South with MySQL?

27;s. > and > starting again with one that does not have so many issues working with > South? -- 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 d

Re: South with MySQL?

DataTable.objects.all() I get "Unknown column 'myapp_datatable.type2stub' in 'field list'". So is there a way to resolve this without deleting the database and starting again with one that does not have so many issues working with South? Regards, Nigel Legg 07914 740972 http:

Re: South with MySQL?

On 2013-08-01, at 11:23 , Nigel Legg wrote: > So are you saying the migration wil or will not work with South using > MySQL?? No. I'm saying if the migration fails the database will be left in an intermediate (and likely incorrect) state. > What do I have to do, in addition to eve

Re: South with MySQL?

So are you saying the migration wil or will not work with South using MySQL?? What do I have to do, in addition to everything in the South documentation, in orde3r to make a South migration work with MySQL, given what you have posted above? Regards, Nigel Legg 07914 740972 http

Re: South with MySQL?

On 2013-08-01, at 10:09 , Nigel Legg wrote: > I tried to run a migration using south, and got the message: > "Since you have a database that does not support running schema-altering > statements in transactions, we have had to leave it in an interim state > between migratio

South with MySQL?

I tried to run a migration using south, and got the message: "Since you have a database that does not support running schema-altering statements in transactions, we have had to leave it in an interim state between migrations." Is this an incompatibility with MySQL, or because my DB is i

Re: South migration ordering on different timeline

it-flow and I use the develop and master branches. > > Since I had to move features ahead of schedule and bring forward to > production, I had to cherry-pick[1] them into the master branch. > > The south migration scripts are not in order anymore and and staging box > is

South migration ordering on different timeline

Hi, I'm using git-flow and I use the develop and master branches. Since I had to move features ahead of schedule and bring forward to production, I had to cherry-pick[1] them into the master branch. The south migration scripts are not in order anymore and and staging box is up to date

Re: Can't convert app to south due to django 1.5 custom User model.

t named 'profiles' which contains a >> custom User model. Here is the declaration of the same: >> >> class CustomUser(AbstractUser): >> image = models.ImageField(_('Image Field'), upload_to='user_images') >> >> I have pointed this in m

Re: Can't convert app to south due to django 1.5 custom User model.

'), upload_to='user_images') > > I have pointed this in my settings module, AUTH_USER_MODEL = > 'profiles.CustomUser' > > and in my settings i have 2 installed apps only, 1. South and 2. profiles. > > when i do syncdb, everything seems to work fine, but

Re: Can't convert app to south due to django 1.5 custom User model.

which contains a custom > User model. Here is the declaration of the same: > > class CustomUser(AbstractUser): > image = models.ImageField(_('Image Field'), upload_to='user_images') > > I have pointed this in my settings module, AUTH_USER_MODEL = &g

Re: Can't convert app to south due to django 1.5 custom User model.

gt; class CustomUser(AbstractUser): >> image = models.ImageField(_('Image Field'), upload_to='user_images') >> >> I have pointed this in my settings module, AUTH_USER_MODEL = >> 'profiles.CustomUser' >> >> and in my settings i ha

Re: Can't convert app to south due to django 1.5 custom User model.

s CustomUser(AbstractUser): > image = models.ImageField(_('Image Field'), upload_to='user_images') > > I have pointed this in my settings module, AUTH_USER_MODEL = > 'profiles.CustomUser' > > and in my settings i have 2 installed apps only, 1. South and 2

Re: South not picking up changes to model, app crashes

Hi > and then where I thought it would find the user_id field.. > python manage.py migrate apppython manage.py syncdb Migrate plays the available migrations but doesn't create a new one. In order to do that, you need to use the schemamigration command. The way to do that is explained here: http

South not picking up changes to model, app crashes

gency_date = models.DateField(blank=True, null=True) description = models.TextField(blank=True, null=True) parts_used = models.TextField(blank=True, null=True) warranty = models.BooleanField(default=False, blank=True) verified = models.BooleanField(default=False, blank=True) I then converted my ap

Re: FailedDryRun-South exeption on migration

On Tue, May 14, 2013 at 1:02 PM, Giorgos Kontogiorgakis wrote: > Thank for all this but i did something terrible and i am afraid of losing > all the work i did! > I was trying to make the dependecies between my tables as i said before!I > was trying to solve this and i used "./manage.py migrate my

Re: FailedDryRun-South exeption on migration

Thank for all this but i did something terrible and i am afraid of losing all the work i did! I was trying to make the dependecies between my tables as i said before!I was trying to solve this and i used "./manage.py migrate myapp 0001" and now i lost everything,my database is empty and i can't

Re: FailedDryRun-South exeption on migration

rface/mysite# ./manage.py migrate > myapp > Running migrations for myapp: > - Migrating forwards to 0048_auto__add_field_linkmap_links. > > myapp:0048_auto__add_field_linkmap_links > FailedDryRun: ! Error found during dry run of > '0048_auto__add_field_linkmap_links'! Aborting. > Traceback (m

FailedDryRun-South exeption on migration

'0048_auto__add_field_linkmap_links'! Aborting. Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/South-0.7.6-py2.7.egg/south/migration/migrators.py", line 175, in _run_migration migration_function() File "/usr/local/lib/py

Re: How to add Foreign Key with SOUTH/DJANGO on existing Database

That's exactly what i did! In my Nodes table i have this one "domains = models.ForeignKey(Domains)" so now i can see the dependecy i want?Or? Is there any way when i press "Domains" on my interface to be able to see the "Nodes" table graphically? -- You received this message because you are sub

  1   2   3   >