From 1e330b6267bf3e6442c12aaa6ec110840291d11e Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Mon, 31 Jul 2006 03:54:51 +0000 Subject: [PATCH] Clarified 'Django no longer requires a database' in docs/release_notes_0.95.txt git-svn-id: http://code.djangoproject.com/svn/django/trunk@3498 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/release_notes_0.95.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/release_notes_0.95.txt b/docs/release_notes_0.95.txt index 72240a57515..d090c0549f8 100644 --- a/docs/release_notes_0.95.txt +++ b/docs/release_notes_0.95.txt @@ -66,7 +66,11 @@ The new features and changes introduced in 0.95 include: * We've made it easier to add custom table-level functions to models, through a new "Manager" API. - * It's now possible to use Django without a database. + * It's now possible to use Django without a database. This simply means + that the framework no longer requires you to have a working database set + up just to serve dynamic pages. In other words, you can just use + URLconfs/views on their own. Previously, the framework required that a + database be configured, regardless of whether you actually used it. * It's now more explicit and natural to override save() and delete() methods on models, rather than needing to hook into the pre_save() and