How to syncdb when adding a new app and south is installed? - django

I've got a Django app with South installed. I added an app ("guardian") in my INSTALLED_APPS. Now when I run python manage.py syncdb I get:
$ python manage.py syncdb
Syncing...
Creating tables ...
Installing custom SQL ...
Installing indexes ...
No fixtures found.
Synced:
> django.contrib.auth
> django.contrib.contenttypes
> django.contrib.sessions
> django.contrib.sites
> django.contrib.admin
> south
Not synced (use migrations):
- myapp
- guardian
and trying the migration returns:
Nothing seems to have changed.
Is there any way to use the original syncdb, not the South one?
Thanks

Are you running manage.py migrate guardian?
"Nothing seems to have changed" looks like an output of running manage.py schemamigration, which wouldn't create any tables to begin with...

You can remove "south" from INSTALLED_APPS then run syncdb and finally, add "south" to INSTALLED_APPS again.

Related

Django Migrations - How can I migrate my own django models without any inbuild models like auth,sessions,sites,admin etc

I have a requirements so that its not possible to change given schema. I dont need any django inbuild models such as admin,auth,sessions,messages etc..
how can I migrate my models without the inbuild models.
I will be gratefull if you can help me.
Thank you.
You can migrate your own models by doing this:
python manage.py makemigrations appname
python manage.py sqlmigrate appname 0001 #It is autogenerated value after makemigrations
python manage.py migrate
This is the way you can do.

Django 1.6.1 and South

I am using south in my Django application and can't understand one thing. I have changed one field from IntegerField to CharField and made after it : manage.py app_name --auto --update. Then I looked at the list of migrations and saw that this migration has number 0014. But when I do manage.py app_name migrate south tries to migrate version 0004. How to specify 0014?
I assume you meant:
manage.py schemamigration app_name --auto --update
not
manage.py app_name --auto --update
You can specify a version with the migrate:
./manage.py migrate app_name 0014
or the full version name:
./manage.py migrate myapp 0014_change_charfield...

How to delete all data for one app in Django 1.4 now that reset is gone?

How do I delete all the data in the database for on Django app? In previous version manage.py reset APPNAME did the job, but that's been deprecated.
What are we supposed to do now if we want to delete all the data from an app using the command line?
reset and sqlreset were both just wrappers around other management commands. sqlreset in particular can be duplicate by simply running:
python manage.py sqlclear myapp
python manage.py sqlall myapp
reset only served to automatically run the result of sqlreset on the database. Personally, I think removing that is a fantastic idea. Still, if you want similar functionality, you can just pipe the output to your database's shell commands.
For PostgreSQL, for example:
python manage.py sqlclear myapp | psql mydatabase
python manage.py sqlall myapp | psql mydatabase
If you want single command that should work with most database types you can pipe the drop table statements, that sqlclear generates, to dbshell
python manage.py sqlclear myapp | python manage.py dbshell
from django.contrib.contenttypes.models import ContentType
for ct in ContentType.objects.all()
ct.model_class().objects.all().delete()
Now that Django integrates migrations by default, you first need to make migrations for your app are first unapplied then deleted.
Here is the command line that works at least with Django 1.8 (replacing by the application you want to delete all associated data and:
# First, update the DB so it thinks no migrations were applied to the app
python manage.py migrate --fake <app_name> zero
# Erase all migrations in the app folder
rm -r "<app_name>/migrations/*"
# Erase the application tables
python manage.py sqlclear <app_name> | python manage.py dbshell
# Recreate the app tables, that will be empty
python manage.py makemigrations <app_name>
python manage.py migrate <app_name>
DIY
If you want to do that from the command line, create the following custom command:
from django.core.management.base import AppCommand, CommandError
from django.utils.six.moves import input
from django.db import DEFAULT_DB_ALIAS, connections
class Command(AppCommand):
help = (
'Removes ALL DATA related to the given app from the database '
'by calling model.objects.all().delete() for all app models. '
'This also removes related data in other apps via cascade.'
)
def add_arguments(self, parser):
super(Command, self).add_arguments(parser)
parser.add_argument(
'--noinput', '--no-input',
action='store_false', dest='interactive', default=True,
help='Tells Django to NOT prompt the user for input of any kind.',
)
parser.add_argument(
'--database', action='store', dest='database', default=DEFAULT_DB_ALIAS,
help='Nominates a database to reset. Defaults to the "default" database.',
)
def handle_app_config(self, app_config, **options):
app_label = app_config.label
database = options['database']
interactive = options['interactive']
db_name = connections[database].settings_dict['NAME']
confirm = (ask_confirmation(app_label, db_name)
if interactive else 'yes')
if confirm == 'yes':
for model in app_config.get_models():
model.objects.using(database).all().delete()
self.stdout.write('Reset done.\n')
else:
self.stdout.write("Reset cancelled.\n")
def ask_confirmation(app_label, db_name):
return input("""You have requested a reset of the application {app_label}.
This will IRREVERSIBLY DESTROY all data related to the app currently in
the {db_name} database, and return each table to empty state.
Are you sure you want to do this?
Type 'yes' to continue, or 'no' to cancel: """.format(**locals()))
Copy it to app/management/commands folder in any of your apps folders and run it with
./manage.py app_db_tables_reset any_installed_app_name
Ready-made package
The command is available in the django_commands package, you can install it with
pip install git+http://github.com/mrts/django-commands.git
and add it to INSTALLED_APPS to activate the command.
Tested with Django 1.9, it may or may not work with 1.8.

django paypal_ipn table does not exist

I am trying to implement django-paypal (dcramer's version) with IPN and although I get the notification, it is answered with a 500 error. I checked my debug log and I saw this message:
DatabaseError: (1146, "Table 'myproject.paypal_ipn' doesn't exist")
none of the tutorials I have found mentioned anything about pypal_ipn table. I also did a syncdb and a south migrate but the table is not created.
What am I doing wrong?
this is what I get with a syncdb:
Synced:
> django.contrib.auth
> django.contrib.contenttypes
> django.contrib.sessions
> django.contrib.sites
> django.contrib.messages
> django.contrib.staticfiles
> debug_toolbar
> grappelli
> filebrowser
> tinymce
> south
> avatar
> django.contrib.admin
> notification
Not synced (use migrations):
- paypal.standard.ipn
$ python manage.py schemamigration main --auto
Nothing seems to have changed.
$ python manage.py migrate main
Running migrations for main:
- Nothing to migrate.
- Loading initial data for main.
No fixtures found.
Try python manage.py migrate. That should migrate the paypal app too.
(Moved from comment to here so the question may be closed. Apparently this did the trick.)
In my case I had to migrate the app explicitly
python manage.py migrate paypal.standard.ipn
If Mike S' solution doesn't work just migrate ipn (this is what worked for me)
python manage.py migrate ipn

syncdb not happening using south for migration

Synced:
> django.contrib.auth
> django.contrib.contenttypes
> django.contrib.sessions
> django.contrib.sites
> django.contrib.messages
> django.contrib.staticfiles
> django.contrib.admin
> django.contrib.admindocs
> kaarya.account
> kaarya.project
> south
Not synced (use migrations):
- kaarya.inspector
(use ./manage.py migrate to migrate these)
Finished "C:\Documents and Settings\EC.32-SAMUEL\workspace\kaarya\kaarya\manage.py syncdb" execution.
I once installed south and tried implementing migration then also prompted as Not synced (use migrations ):
Note : Here kaarya is my project and inspector is the app i tried migrating once using south but was not successful
Did you try
python manage.py migrate
If so what was the error?