gpt4 book ai didi

django - 如何管理非默认 Django 数据库

转载 作者:行者123 更新时间:2023-11-29 11:22:34 25 4
gpt4 key购买 nike

我在 Django (v1.8) 应用程序中使用非默认数据库时遇到问题。当我尝试 makemigrations 并迁移 PostgreSQL 数据库没有得到更新。

这是我的 Django 结构:

fbrDjangoSite
|-- db.sqlite3
|-- manage.py
|-- fbrDjangoSite
| |-- __init__.py
| |-- requirements.txt
| |-- settings.py
| |-- urls.py
| |-- wsgi.py
|-- fbrPostHasteAppV0_1
| |-- __init__.py
| |-- admin.py
| |-- migrations
| |-- models.py
| |-- router.py
| |-- tests.py
| |-- urls.py
| |-- views.py

fbrPostHasteAppV0_1/admin.py

from django.contrib import admin
from fbrPostHasteAppV0_1.models import MusicianTable # gvim ../fbrPostHasteAppV0_1/models.py +/MusicianTable
from fbrPostHasteAppV0_1.models import AlbumTable # gvim ../fbrPostHasteAppV0_1/models.py +/AlbumTable

# Register your models here.
admin.site.register(MusicianTable)
admin.site.register(AlbumTable)

fbrPostHasteAppV0_1/models.py

from django.db import models

# Define your models/tables here.
class MusicianTable(models.Model):
first_name = models.CharField(max_length=50)
last_name = models.CharField(max_length=50)
instrument = models.CharField(max_length=100)

class Meta:
managed = True

class AlbumTable(models.Model):
artist = models.ForeignKey(MusicianTable)
name = models.CharField(max_length=100)
release_date = models.DateField()
num_stars = models.IntegerField()

class Meta:
managed = True

fbrPostHasteAppV0_1/router.py

class fbrPostHasteAppV0_1Router(object):
def db_for_read(self, model, **hints):
if model._meta.app_label == 'fbrPostHasteAppV0_1':
return 'fbrPostHasteDbV0_1'
return None

def db_for_write(self, model, **hints):
if model._meta.app_label == 'fbrPostHasteAppV0_1':
return 'fbrPostHasteDbV0_1'
return None

def allow_syncdb(self, db, model):
if db == 'fbrPostHasteDbV0_1':
return model._meta.app_label == 'fbrPostHasteAppV0_1'
elif model._meta.app_label == 'fbrPostHasteAppV0_1':
return False
return None

fbrDjangoSite/settings.py

# ...
INSTALLED_APPS = (
# ...
'fbrPostHasteAppV0_1', # v ../fbrPostHasteAppV0_1/__init__.py
)

DATABASES = {
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
},
# ...
'fbrPostHasteDb': {
'ENGINE': 'django.db.backends.postgresql_psycopg2',
'NAME': 'fbrPostHasteDbV0_1',
'USER': 'myuser',
'PASSWORD': '',
'HOST': 'myhost.us.overlord.com',
'PORT': '0000',
},
}

DATABASE_ROUTERS = ['fbrPostHasteAppV0_1.router.fbrPostHasteAppV0_1Router',]

这是我运行迁移命令时的输出:

[fbrDjangoServerV0_1.venv.py] /<3>django/fbrDjangoServerV0_1.venv.py/fbrDjangoSite> python manage.py makemigrations fbrPostHasteAppV0_1 --verbosity 3
/fobar-tools/pylibs/lib/python/Django-1.8-py2.7.egg/django/db/models/base.py:1497: RemovedInDjango19Warning: Router.allow_syncdb has been deprecated and will stop working in Django 1.9. Rename the method to allow_migrate.
if not router.allow_migrate(db, cls):
Did you rename the fbrPostHasteAppV0_1.Musician model to MusicianTable? [y/N] y
Migrations for 'fbrPostHasteAppV0_1':
0002_auto_20150408_1653.py:
- Create model AlbumTable
- Rename model Musician to MusicianTable
- Remove field artist from album
- Delete model Album
- Add field artist to albumtable
[fbrDjangoServerV0_1.venv.py] /<3>django/fbrDjangoServerV0_1.venv.py/fbrDjangoSite> python manage.py migrate --verbosity 3
/fobar-tools/pylibs/lib/python/Django-1.8-py2.7.egg/django/db/models/base.py:1497: RemovedInDjango19Warning: Router.allow_syncdb has been deprecated and will stop working in Django 1.9. Rename the method to allow_migrate.
if not router.allow_migrate(db, cls):
Operations to perform:
Synchronize unmigrated apps: staticfiles, messages
Apply all migrations: fbrSimDataV0_2, sessions, admin, polls, auth, contenttypes, fbrPostHasteAppV0_1
Synchronizing apps without migrations:
/fobar-tools/pylibs/lib/python/Django-1.8-py2.7.egg/django/db/utils.py:336: RemovedInDjango19Warning: Router.allow_syncdb has been deprecated and will stop working in Django 1.9. Rename the method to allow_migrate.
return [model for model in models if self.allow_migrate(db, model)]
Creating tables...
Installing custom SQL...
Installing indexes...
Running migrations:
Applying fbrPostHasteAppV0_1.0002_auto_20150408_1653.../fobar-tools/pylibs/lib/python/Django-1.8-py2.7.egg/django/db/migrations/operations/base.py:107: RemovedInDjango19Warning: Router.allow_syncdb has been deprecated and will stop working in Django 1.9. Rename the method to allow_migrate.
router.allow_migrate(connection_alias, model) and
OK
/fobar-tools/pylibs/lib/python/Django-1.8-py2.7.egg/django/contrib/auth/management/__init__.py:70: RemovedInDjango19Warning: Router.allow_syncdb has been deprecated and will stop working in Django 1.9. Rename the method to allow_migrate.
if not router.allow_migrate(using, Permission):
The following content types are stale and need to be deleted:
fbrPostHasteAppV0_1 | album
fbrPostHasteAppV0_1 | musician

但是当我查看 dtatbase 时,还没有添加“表”。

[fbrDjangoServerV0_1.venv.py] /<3>django/fbrDjangoServerV0_1.venv.py/fbrDjangoSite>       psql -h localhost -p 0000 --command "\l" postgres
List of databases
Name | Owner | Encoding | Collate | Ctype | Access privileges
-----------+----------+-----------+---------+-------+-----------------------
postgres | myuser | SQL_ASCII | C | C |
template0 | myuser | SQL_ASCII | C | C | =c/myuser +
| | | | | myuser=CTc/myuser
template1 | myuser | SQL_ASCII | C | C | =c/myuser +
| | | | | myuser=CTc/myuser
test | myuser | SQL_ASCII | C | C |
(4 rows)

我的印象是 Django 可以创建表格并将其保存在每当我对模型进行更改时同步。我的理解是否正确,如果那么我在这里做错了什么?

更新

我的一个问题是我的路由器代码是基于旧版本的 Django 。我不确定这现在是否完全正确,但它非常类似于现在的文档:https://docs.djangoproject.com/en/1.8/topics/db/multi-db/

class fbrPostHasteAppV0_1Router(object):
def db_for_read(self, model, **hints):
if model._meta.app_label == 'fbrPostHasteAppV0_1':
return 'fbrPostHasteDbV0_1'
return None

def db_for_write(self, model, **hints):
if model._meta.app_label == 'fbrPostHasteAppV0_1':
return 'fbrPostHasteDbV0_1'
return None

def allow_relation(self, obj1, obj2, **hints):
if obj1._meta.app_label == 'fbrPostHasteAppV0_1' or \
obj2._meta.app_label == 'fbrPostHasteAppV0_1':
return True
return None

def allow_migrate(self, db, app_label, model=None, **hints):
if app_label == 'fbrPostHasteAppV0_1':
return db == 'fbrPostHasteDbV0_1'
return None

另一个问题是我没有使用 --database 调用 migrate:

 python manage.py migrate --database=fbrPostHasteDb

但是现在我又遇到了另一个错误:

django.db.utils.OperationalError: FATAL:  database "fbrPostHasteDbV0_1" does not exist

继续弄清楚我搞砸了什么......

更新 2

所以我创建了这样的数据库:

psql -h localhost -p 8080 --command "CREATE DATABASE fbrPostHasteDbV0_1"

但它创建了 fbrposthastedbv0_1。

所以一旦我更改了所有引用和名称,我就可以:

python manage.py migrate --database=fbrPostHasteDb

最佳答案

你将不得不手动更改必要的字段,我不确定确切的 postgres 错误,但我在一个月前处理过类似的情况。迁移有时很痛苦,但在修复它们后报告给:

https://docs.djangoproject.com/en/1.8/internals/contributing/bugs-and-features/

关于django - 如何管理非默认 Django 数据库,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/29526341/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com