On Mar 28, 9:34 pm, andy baxter <[EMAIL PROTECTED]>
wrote:
> Peter Rowell wrote:
> >> So should I just create two classes that are identical but name one
> >> CurrentElectionResults and the other PastElectionResults?
>
> Can't you just have a single class 'ElectionResults' and add a field
> called 'current'?
>
> I'm planning on doing something similar with my app.
>
> andy.
I could do that, but I'd like to keep my current election results in
its own table since I will be importing data through a CSV file. The
CSV file will get updated frequently over the course of about 2
hours. Because of this, I plan to either wipe all data from my
results table before importing the CSV file. This is why I want
separate tables. One results table would hold all the past election
results while the other would get the imports from the CSV file.
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
