Stefan, In my apps I do TONS of offline processing, but an able to have users tweak things using the Admin interface.
I haven't had any issues with caching or outdated data. Good luck! Corey Oordt On Oct 16, 2006, at 11:19 AM, Stefán Freyr Stefánsson wrote: > Hello. > > I have a deadline on a project coming up so I'm hoping that you > will forgive me for posting a question that I could technically > experiment with myself but because of the deadline I would very > much like to receive input from the django community on whether my > time is well spent on doing this or not. > > So the thing is that I have an application that updates a database > table. I'm currently working on this application and soon I will > start working on a web frontend for displaying this data. > > My question is whether Django is a good choice for me. What I'm > mostly worried about is if Django has some sort of a caching > mechanisme that is hard to "turn off", making it vulnerable to not > picking up changes to the data that is done by external processes. > > What I plan on doing is create my model in Django just like I > usually do and then use Django to create the tables and > everything... then I'll modify my external application so that it > pushes data into the db structure that Django produced. > > If anyone has some reading material on this or experience (s)he > would like to share, I'd very much appreciate it. I'm especially > looking for pitfalls that you guys might let me know of in advance > to avoid because of my looming deadline. > > Kind regards, Stefan Freyr. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
