On 10/4/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Django's database-centric approach seems to make certain kinds of
> mostly-static sites harder to build. For example, most of what I want
> to put on my site is probably going to come from RestructuredText
> source, but that source isn't going to change in response to user
> interaction. Yes, I could set up a ReST_page model and store the text
> in the database, but that has some real disadvantages as compared with
> keeping the content in my SVN repository along with the rest of the
> code, css, images, and other elements that are not going to be changed
> by user interaction:
Hi Dave,
If you just want to use the HTTP request/response part of Django,
there's no requirement that you need to use a database.
All Django cares about is that your view functions return an
HttpResponse. What they do internally -- whether it's connecting to a
database, or connecting to your ReStructured Text source -- is
entirely up to you.
def my_view(request):
t = get_my_restructured_text()
return render_to_response('mytemplate', {'text': t})
There is no reason you'd have to store your text in a database, except
if you wanted your text to be edited by Django's admin interface. But
if you're using SVN to manage your data, you wouldn't want that,
anyway.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
