On Jul 22, 2008, at 3:55 PM, Philip Semanchuk wrote:
>
> In our app, SQLite has big advantages over other databases so I don't
> mind deepening our ties to it. It won't be going away anytime soon.
> Being bound to a specific table structure is indeed less appealing and
> that's my main objection to my proposed solution. As you point out, a
> higher level filter concept would provide a layer of abstraction and
> insulation against schema changes. To that end, I tried pickling a
> Query object but it didn't seem to like it ("Can't pickle <class
> 'sqlalchemy.orm.properties.ColumnComparator'>: it's not found as
> sqlalchemy.orm.properties.ColumnComparator") which is OK. That was a
> shot in the dark, and I'm not sure it would be any wiser than just
> storing raw SQL.
>
you can pickle clause expressions. On Query, its available as
query.whereclause. Though if you dont greatly restrict and parse the
expressions you're storing then you still have dependencies on table
structure.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
