[sqlalchemy] An update and some questions

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.

[sqlalchemy] Re: Differentiate ANSIIdentifierPreparer.format_column select clause from where clause??

i suppose this is not terribly hard since it would just mean some extra argument passed along. of course the question is *why* would you need this. if its some kind of case-insensitive resultproxy issue, id rather do something on that end. It's not about case in the resultproxy, it's about

[sqlalchemy] Re: 4 errors since upgrade from 0.3.3 to 0.3.4

i cant do anything without example code reproducing the issues. the first error in particualr seems clear that its a user-configuration issue, which is perhaps cascading to the rest of the issues. On Feb 17, 2007, at 11:47 PM, Yves-Eric wrote: Hi all, I am porting an existing webapp

[sqlalchemy] Re: Mappers and sessions

a lazy loader calls a function object_session(instance) to locate the current session to which an instance is bound. this function is a simple hash lookup and is defined in sqlalchemy.orm.session. On Feb 18, 2007, at 12:51 PM, Paul Johnston wrote: Hi, A plain old mapper isn't attached

[sqlalchemy] Re: An update and some questions

On Feb 18, 2007, at 3:35 PM, Paul Johnston wrote: 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

[sqlalchemy] Re: Differentiate ANSIIdentifierPreparer.format_column select clause from where clause??

On Feb 18, 2007, at 6:37 PM, Troy wrote: i suppose this is not terribly hard since it would just mean some extra argument passed along. of course the question is *why* would you need this. if its some kind of case-insensitive resultproxy issue, id rather do something on that end. It's

[sqlalchemy] Re: 4 errors since upgrade from 0.3.3 to 0.3.4

I am also suspecting the 1st issue to cascade down to the rest. Here is some stripped down code, reproducing the first issue. Please let me know if I am doing anything wrong. Again, this works fine with 0.3.3: ### # Here is the database creation

[sqlalchemy] Re: 4 errors since upgrade from 0.3.3 to 0.3.4

Thanks for the quick reply. The dummy polymorphic_identity workaround fixed everything. Oh, and I see you have already committed a fix to SVN. Great reactivity! FWIW, the check got in at rev. 2221: http://www.sqlalchemy.org/trac/changeset/2221 Thanks again, great support! -- Yves-Eric