diff options
| author | Adrian Holovaty <adrian@holovaty.com> | 2006-07-31 03:54:51 +0000 |
|---|---|---|
| committer | Adrian Holovaty <adrian@holovaty.com> | 2006-07-31 03:54:51 +0000 |
| commit | 1e330b6267bf3e6442c12aaa6ec110840291d11e (patch) | |
| tree | 3ee64e98d64a9c3ed43c72a12521ae6b1be8d73e /docs | |
| parent | c4652993a26268ef4908c72336db18c779037f12 (diff) | |
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
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/release_notes_0.95.txt | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/release_notes_0.95.txt b/docs/release_notes_0.95.txt index 72240a5751..d090c0549f 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 |