migrate

from flask import Flask from flask.ext.sqlalchemy import SQLAlchemy from flask.ext.migrate import Migrate, MigrateCommand from flask.ext.script import Manager app = Flask(__name__) app.config[ 'SQLALCHEMY_DATABASE_URI'] = 'sqlite:///test.db' db = SQLAlchemy(app) migrate = Migrate(app, db) manager = Manager(app) manager.add_command( 'db', MigrateCommand) class Post(db.Model): id = db.Column(db.Integer, primary_key= True) name = db.Column(db.String( 80)) category_id = db.Column(db.Integer, db.ForeignKey( 'category.id')) category = db.relationship( 'Category', backref=db.backref( 'posts', lazy=

any easy way to detect it? I want to skip some codes in envirmonment.rb when doing migration rake. I had this problem in a legacy application I was maintaining. There were some observers that were interfering with migrations past a certain point, so I disabled them during migration by checking the application name and arguments # Activate observers that should always be running # config.active_record.observers = :cacher, :garbage_collector, :forum_observer# observers break a migrate from VERSION xxx - disable them for rake db:migrate unless ( File.basename($0) == "rake" && ARGV.include?("db

I'm using AbstractBaseUser for my user models in various projects. Updating to Django 1.8 RC1 works smoothly and I can run the migrate management command. However, when trying to create a fresh database table layout from scratch, I get the following error: python manage.py migrate >>> ... >>> ... >>> django.db.utils.ProgrammingError: relation "auth_group" does not exist All works perfectly with Django 1.7.x and I cannot find anything about this issue elsewhere. So, is it a big with the RC1 version or did something change that I'm not aware of in Django 1.8? Unfortunately, the error message

I have a PostgreSQL 9.1 database with 100 or so tables that were loaded into the 'public' schema. I would like to move those tables (but not all of the functions in 'public') to a 'data' schema. I know that I can use the following to move 1 table at a time. ALTER TABLE [tablename] SET SCHEMA [new_schema] Is it possible to move all of the tables to the new schema in one operation? If so, what would be the most efficient way to accomplish this task? DO will do the trick: DO $$ DECLARE row record; BEGIN FOR row IN SELECT tablename FROM pg_tables WHERE schemaname = 'public' -- and other conditions

I'm really new in programming and I wanted to follow the Djangogirls tutorial, but I'm stucked now. In the tutorial, I am here : To create a database for our blog, let's run the following in the console: python manage.py migrate (we need to be in the djangogirls directory that contains the manage.py file). If that goes well, you should see something like this: ... There is no option to fail in the tutorial but I have an error message: (myvenv) C:\Users\Julcsi\djangogirls> python manage.py migrate Traceback (most recent call last): File "manage.py", line 22, in <module> execute_from_command