Re: New to Django / Web Development [ Confused About When to Store To Database For Static Content]

I think you answered the question yourself, if something rarely changes the only reason to store it in a db would be for convenience. Static pages are more successfully cached.

---jerry

On Sat, Dec 22, 2012 at 5:43 PM, Django Son <i.ask.django.questions@gmail.com> wrote:

Hi there, :)

I'm a complete beginner at webdev and had a question about when to store to a database for content that seldom changes. I understand the need to access and modify a database for dynamic content but what about static content? For instance, lets say my website has a large number of paragraphs that don't change. Is there a performance benefit for saving these in a database or is it solely for more modularity? When it comes to static content, how do I know the line between when I should save it to a database and when to hard-code it into a template?

Thanks ahead of time for any help!

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/UQViv1laBMsJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--

Gerald Klein DBA

ContactMe@geraldklein.com

www.geraldklein.com

geraldklein.wordpress.com

jk@zognet.com

708-599-0352

Arch Awesome, Ranger & Vim the coding triple threat.

Linux registered user #548580 

--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.