Annikka/evennia
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

Updated ReST docs, fixed some things in Swedish translation.

Browse source
This commit is contained in:
Griatch 2012-02-19 10:49:59 +01:00
parent 11e61255da
commit c4f2c493d9
19 changed files with 937 additions and 745 deletions
Download patch file Download diff file Expand all files Collapse all files

27
docs/sphinx/source/wiki/ChoosingAnSQLServer.rst
View file

@ -13,17 +13,19 @@ SQLite
------
This is the default database used, and for the vast majority of Evennia
installs it will probably be more than adequate. No server process is
needed, the administrative overhead is tiny (as is resource
consumption). The database will appear as a simple file
(``game/evennia.db3``). It is not tested how well Evennia performs with
SQLite under a heavier load, but it should probably be fine for most
normal mud-related usage.
installs it will probably be more than adequate for a long time. No
server process is needed, the administrative overhead is tiny (as is
resource consumption). The database will appear as a simple file
(``game/evennia.db3``). SQLite is excellent for development and easy
testing. The database is however hampered in speed by not allowing
concurrent reads. For a full production game with many users accessing
the database, a more fully featured database engine (MySQL, Postgres
etc) is probably better.
**Note:** If you run Windows and for some reason need to use a
third-party web server like Apache rather than Evennia's internal web
server, sqlite is probably not be the best choice. This is due to the
possibility of clashes with file-locking of the database file under
server, sqlite is probably also not be the best choice. This is due to
the possibility of clashes with file-locking of the database file under
Windows.
Postgres
@ -34,12 +36,17 @@ aspiring to grow to a larger size. While not as fast as SQLite for
simple purposes, it will scale infinitely better than SQLite, especially
if your game has an extensive web presence.
**Warning:** Postgres has issues with Evennia on some installs at the
moment. "http://code.google.com/p/evennia/issues/detail?id
151">Issue 151 outlines this. If unsure, avoid Postgres for now.
MySQL
-----
MySQL **may** be slightly faster than Postgres depending on your setup
and software versions involved. Older versions had some peculiarities
though, so check out Django's `Notes about supported
and software versions involved. Older versions of MySQL had some
peculiarities though, so check out Django's `Notes about supported
Databases <http://docs.djangoproject.com/en/dev/ref/databases/#ref-databases>`_
to make sure you use the correct version.