From 1b80c99efc567d777f0ed022014546a6d651193b Mon Sep 17 00:00:00 2001 From: kedder Date: Mon, 10 Mar 2003 20:23:41 +0000 Subject: [PATCH] Advertising mysql git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/trunk@1583 57a73879-2fb5-44c3-a270-3262357dd7e2 --- doc/installation.txt | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/doc/installation.txt b/doc/installation.txt index 1ad0333..425784c 100644 --- a/doc/installation.txt +++ b/doc/installation.txt @@ -2,7 +2,7 @@ Installing Roundup ================== -:Version: $Revision: 1.37 $ +:Version: $Revision: 1.38 $ .. contents:: @@ -212,6 +212,13 @@ There's several to choose from, each with benefits and limitations: This uses the SQLite_ embedded RDBMS to provide a fast, scaleable backend. There are no limitations, and it's much faster and more scaleable than the dbm backends. +**mysql** + Backend for popular RDBMS MySQL. This backend uses MySQL's Berkeley DB + (transaction safe) table format, so with small amount of data it may be a + bit slower than *dbm backends (due to mysql layer's overhead). However with + lots of data mysql may perform better (due to query optimisation). No actual + serious benchmarks were made though. For more info on installation of this + backend see doc/mysql.txt. **metakit** This backend is implemented over the metakit_ storage system, using Mk4Py as the interface. It scales much better than the dbm backends. -- 2.30.2