preventing data from getting saved to the backend database?

I'm a newbie reading documentation, and this question may well be
answered by something I havent read yet, but anyway...

My understanding so far is that django incorporates a back-end
database (in my case built in sql3 on windows) to which all model
related data from forms gets posted.

I'm trying to write an app whereby the user can upload 2 sets of alarm
files: a before and an after view, and then be able to filter and zoom
in detail appropriately. However, each alarm file upload might
comprise several hundred alarms.
I'm only really interested in comparing these 2 sets of alarms, but it
seems to me that by using django (and an alarm Class etc), that all
these alarms will be pasted into the database every time a report is
requested. That's not what I want, and at 2 x 200+ alarms per request,
I can imagine me clogging up my alarms database at some point (but
more importantly bloating with data I don't want to keep...).

I'm sure there is a solution, could someone please tell me their
thoughts? - what do I do with lots of data that I don't want to keep
after a specific session is finished?

--
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.