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

Updated rst files to latest wiki.

Browse source
This commit is contained in:
Griatch 2011-09-20 13:21:07 +02:00
parent 60424fa828
commit 9a719d7fb0
8 changed files with 82 additions and 63 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -12,17 +12,13 @@ page.
SQLite
------
This is the default database used, and for the vast majority of sites
out there, will probably be more than adequate. No server process is
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.db`` by default). Purging your database is just a matter
of deleting this file and re-running the database creation commands in
GettingStarted.
It is not tested how well Evennia performs with SQLite under a heavier
load, but it should probably be fine given the relative simplicity of
our applications.
(``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.
**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
@ -33,23 +29,19 @@ Windows.
Postgres
--------
This is Django's recommended DB engine, and the one that we recommend
for all sites 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.
This is Django's recommended database engine, usable for all sites
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.
MySQL
-----
While perfectly reasonable to deploy under, the MySQL driver for Django
has some very slight oddities (at the time of this document's writing)
that probably don't affect our usage case that much (if at all). Make
sure you look at the aforementioned `Notes about supported
Databases <http://docs.djangoproject.com/en/dev/ref/databases/#ref-databases>`_
page for the latest on this.
MySQL **may** be slightly faster than Postgres depending on your setup
and software versions involved.
and software versions involved. Older versions 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.
Others
------