My motivation for using the Django ORM layer was simply to reuse the logic that parses text values to native values (html2python) and any column name mapping that goes on, both of which are managed by the *Field members. I know that's not a huge win, but since I'm at an early point in the project where I'm tweaking the schema quite a bit, its nice to know if I change an int field to a float, or add another field that was previously being skipped from the file, or rename a column, it just works. But I see your point - it remains to be seen if I'm getting enough benefit to justify this approach.
Speed really isn't an issue right now. Each file takes a few seconds to load (up to a minute for the really large ones) and they run as scheduled jobs over night. And this is all running on a VMWare virtual machine on my lowly Dell desktop - I could copy the VM to a server and get a huge boost. If I _really_ cared about speed, since I'm using MySQL, I'd consider mapping a table directly to the file via the CSV storage engine and then just copy it from the CSV table to a "real" table. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
