Peter Bengtsson wrote:
>> Yep, that's prettymuch what I ended up writing. Wow, Django's ORM
>> expressions are ugly compared to SQLAlchemy ;-)
>>
> Then just
> import sqlalchemy
Yes, because that obviously provides a drop-in replacement for all users
of Django's ORM ;-)
> If the db is a legacy database and things are stored as varchars then
> I don't see any point in changing the database so you can use proper
> datetimes.
> And if it's indexed searching for something like 'April 2009' is going
> to be uber fast.
The legacy database was ZODB, which was the problem. The data took up
about 14GB on disk in ZODB. About 1GB in Postgres....
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
