On 9/25/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > On Sep 24, 2007, at 11:36 PM, m h wrote: > > > > > NP, I know Oracle is a drag.... but that's what the client has. > > Perhaps if you could clarify why I'm confused I might be able to help > > debug. (I've stepped through expression.py all day long). I feel > > like I just need a little hint or push in the right direction. > > > > Eventually you get to a cx cursor and call execute with the statement > > on it. How does the same statement/parameter combo fail with SQL > > generate, yet succeed using `text` or plain cx? If I can get over > > that hump, I think I might be able to give you a patch. > > > > my suspicion is that we are calling set_input_sizes on the cursor in > the case of oracle. but im not sure (need to play with it). if you > want to try unsetting that flag in the oracle dialect...(its called > "auto_setinputsizes" or similar). > > Thanks for the explanation, it all makes sense now. That was what I needed. If I pass auto_setinputsizes=False to create_engine it works!
Just need to figure out where OracleCompiler.binds is set. None of my breakpoints for .binds are getting hit in compiler.py --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
