Added a fix for running with postgresql-psycopg2. This does not actually resolve the problem as much as circumvent it, so I'm not marking Issue 115 as closed just yet.
This commit is contained in:
parent
f15e26c54a
commit
9e2ad59663
5 changed files with 48 additions and 24 deletions
|
|
@ -121,8 +121,7 @@ ATTRIBUTE_CACHE_MAXSIZE = 100
|
|||
# Evennia Database config
|
||||
######################################################################
|
||||
|
||||
# Database config syntax for Django 1.2+. You can add several
|
||||
# database engines in the dictionary (untested).
|
||||
# Database config syntax for Django 1.2+.
|
||||
# ENGINE - path to the the database backend (replace
|
||||
# sqlite3 in the example with the one you want.
|
||||
# Supported database engines are
|
||||
|
|
@ -142,7 +141,7 @@ DATABASES = {
|
|||
'HOST':'',
|
||||
'PORT':''
|
||||
}}
|
||||
# Engine Config style for Django versions < 1.2. See above.
|
||||
# Engine Config style for Django versions < 1.2 only. See above.
|
||||
DATABASE_ENGINE = 'sqlite3'
|
||||
DATABASE_NAME = os.path.join(GAME_DIR, 'evennia.db3')
|
||||
DATABASE_USER = ''
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue