Hi, I've been working away on a few SQLAlchemy things this week-end. Some updates, and some questions:
1) I've posted a recipe for processing nested Python hash/list structures into the database. This is handy for me, for saving data returned by FormEncode. http://www.sqlalchemy.org/trac/wiki/UsageRecipes/ProcHash 2) In MS-SQL a few problems are caused by strings with no specified length being created as TEXT. The TEXT type doesn't support various operations, such as LIKE. I wonder if it would be better to create such columns as VARCHAR(MAX). People who really wanted TEXT could still explicitly specify that. 3) ExecutionContext.post_exec isn't called if there's an error during the query. MS-SQL has some code that needs to ALWAYS be run after a query. Is there a good place to put this? I thought about Dialect.do_execution, it doesn't seem to have access to the ExecutionContext object. 4) I'm considering submitting a patch to make _CompoundClause.compare tell you if the clause has the same semantics as the comparison (at the moment it tells if they're exactly the same). This would make "t1.a = t2.a AND t1.b = t2.b" equal "t1.b = t2.b AND t1.a = t2.a" which to me makes sense. Is this likely to be accepted? That's all folks! Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
