Author: russellm
Date: 2009-06-24 09:19:44 -0500 (Wed, 24 Jun 2009)
New Revision: 11098
Modified:
django/branches/releases/1.0.X/docs/ref/databases.txt
django/branches/releases/1.0.X/docs/topics/install.txt
Log:
[1.0.X] Fixed #11356 -- Added links to the growing collection of 3rd party
database backends that are available. Thank to Nathan Auch for the draft text.
Merge of r11093 from trunk.
Modified: django/branches/releases/1.0.X/docs/ref/databases.txt
===================================================================
--- django/branches/releases/1.0.X/docs/ref/databases.txt 2009-06-24
14:04:18 UTC (rev 11097)
+++ django/branches/releases/1.0.X/docs/ref/databases.txt 2009-06-24
14:19:44 UTC (rev 11098)
@@ -198,7 +198,7 @@
DATABASE_OPTIONS = {
'read_default_file': '/path/to/my.cnf',
}
-
+
# my.cnf
[client]
database = DATABASE_NAME
@@ -365,10 +365,10 @@
* Switching to another database backend. At a certain point SQLite becomes
too "lite" for real-world applications, and these sorts of concurrency
errors indicate you've reached that point.
-
- * Rewriting your code to reduce concurrency and ensure that database
+
+ * Rewriting your code to reduce concurrency and ensure that database
transactions are short-lived.
-
+
* Increase the default timeout value by setting the ``timeout`` database
option option::
@@ -377,7 +377,7 @@
"timeout": 20,
# ...
}
-
+
This will simply make SQLite wait a bit longer before throwing "database
is locked" errors; it won't really do anything to solve them.
@@ -521,3 +521,28 @@
Oracle. A workaround to this is to keep ``TextField`` columns out of any
models that you foresee performing ``distinct()`` queries on, and to
include the ``TextField`` in a related model instead.
+
+.. _third-party-notes:
+
+Using a 3rd-party database backend
+==================================
+
+In addition to the officially supported databases, there are backends provided
+by 3rd parties that allow you to use other databases with Django:
+
+* `Sybase SQL Anywhere`_
+* `IBM DB2`_
+* `Microsoft SQL Server 2005`_
+* Firebird_
+* ODBC_
+
+The Django versions and ORM features supported by these unofficial backends
+vary considerably. Queries regarding the specific capabilities of these
+unofficial backends, along with any support queries, should be directed to
+the support channels provided by each 3rd party project.
+
+.. _Sybase SQL Anywhere: http://code.google.com/p/sqlany-django/
+.. _IBM DB2: http://code.google.com/p/ibm-db/
+.. _Microsoft SQL Server 2005: http://code.google.com/p/django-mssql/
+.. _Firebird: http://code.google.com/p/django-firebird/
+.. _ODBC: http://code.google.com/p/django-pyodbc/
Modified: django/branches/releases/1.0.X/docs/topics/install.txt
===================================================================
--- django/branches/releases/1.0.X/docs/topics/install.txt 2009-06-24
14:04:18 UTC (rev 11097)
+++ django/branches/releases/1.0.X/docs/topics/install.txt 2009-06-24
14:19:44 UTC (rev 11098)
@@ -61,14 +61,28 @@
Get your database running
=========================
-If you plan to use Django's database API functionality, you'll need to
-make sure a database server is running. Django works with PostgreSQL_,
-MySQL_, Oracle_ and SQLite_ (although SQLite doesn't require a separate server
-to be running).
+If you plan to use Django's database API functionality, you'll need to make
+sure a database server is running. Django supports many different database
+servers and is officially supported with PostgreSQL_, MySQL_, Oracle_ and
+SQLite_ (although SQLite doesn't require a separate server to be running).
-Additionally, you'll need to make sure your Python database bindings are
-installed.
+In addition to the officially supported databases, there are backends provided
+by 3rd parties that allow you to use other databases with Django:
+* `Sybase SQL Anywhere`_
+* `IBM DB2`_
+* `Microsoft SQL Server 2005`_
+* Firebird_
+* ODBC_
+
+The Django versions and ORM features supported by these unofficial backends
+vary considerably. Queries regarding the specific capabilities of these
+unofficial backends, along with any support queries, should be directed to the
+support channels provided by each 3rd party project.
+
+In addition to a database backend, you'll need to make sure your Python
+database bindings are installed.
+
* If you're using PostgreSQL, you'll need the psycopg_ package. Django supports
both version 1 and 2. (When you configure Django's database layer, specify
either ``postgresql`` [for version 1] or ``postgresql_psycopg2`` [for
version 2].)
@@ -89,6 +103,9 @@
:ref:`Oracle backend <oracle-notes>` for important information
regarding supported versions of both Oracle and ``cx_Oracle``.
+* If you're using an unofficial 3rd party backend, please consult the
+ documentation provided for any additional requirements.
+
If you plan to use Django's ``manage.py syncdb`` command to
automatically create database tables for your models, you'll need to
ensure that Django has permission to create and alter tables in the
@@ -111,7 +128,11 @@
.. _pysqlite: http://pysqlite.org/
.. _cx_Oracle: http://cx-oracle.sourceforge.net/
.. _Oracle: http://www.oracle.com/
-
+.. _Sybase SQL Anywhere: http://code.google.com/p/sqlany-django/
+.. _IBM DB2: http://code.google.com/p/ibm-db/
+.. _Microsoft SQL Server 2005: http://code.google.com/p/django-mssql/
+.. _Firebird: http://code.google.com/p/django-firebird/
+.. _ODBC: http://code.google.com/p/django-pyodbc/
.. _removing-old-versions-of-django:
Remove any old versions of Django
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
