summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-01-17 17:07:52 +0000
committerChris McDonough <chrism@agendaless.com>2009-01-17 17:07:52 +0000
commit49127a2670f2a96d9f4af07acca1caaf064002f1 (patch)
treecd45f75e0dd97c1a1ce7809f759d8e7083033975
parentc0c1885413d1b92add5ef198279e49ba37a0ee2d (diff)
downloadpyramid-49127a2670f2a96d9f4af07acca1caaf064002f1.tar.gz
pyramid-49127a2670f2a96d9f4af07acca1caaf064002f1.tar.bz2
pyramid-49127a2670f2a96d9f4af07acca1caaf064002f1.zip
More.
-rw-r--r--docs/narr/introduction.rst12
1 files changed, 12 insertions, 0 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index 836f57c44..5943e97ae 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -95,6 +95,18 @@ during :mod:`repoze.bfg` application development. Instead, the
:mod:`repoze.bfg` framework tends to "hide" most interaction with the
CA behind special-purpose API functions.
+Also unlike :term:`Zope` and unlike other "full-featured" frameworks
+such as :term:`Django`, :mod:`repoze.bfg` makes no assumptions about
+what persistence mechanisms you want to use to build an application.
+Zope applications are typically reliant on :term:`ZODB`;
+:mod:`repoze.bfg` allows you to build :term:`ZODB` applications, but
+it has no reliance on the ZODB package. Likewise, :term:`Django`
+tends to make the assumption that you're going to want to store your
+application's data in a relational database. :mod:`repoze.bfg` makes
+no such assumption; it allows you to use a relational database but
+doesn't enourage or discourage an application developer about such a
+decision.
+
Why?
----