Thanks for the response! On 9/22/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > well the issue is not even the bind params its the result coming back > from cx_oracle.
Again, I'm confused how this query works from straight cx and .3.7 but fails when .4beta calls it. Could you enlighten me on what I'm missing? its not well documented/consistent which oracle > types come back as a LOB and also come back with a cx_oracle LOB > object, and which ones do not. its possible that just upgrading > your cx_oracle will fix the issue here...see if you can try that > first (and possibly identify which column in that SQL statement might > be LOB-like). Upgraded to cx_Oracle 4.3.1 from 4.2 and got the same error. All the varchar2 columns have sizes (between 2 and 50) Also keep in mind if you are using any String column > types without a length, they come back as LOBs as well. As I said above it appears that all the strings come with lengths. But doesn't the error indicate that a string (CLOB/VARCHAR) appeared where a NUMBER was expected? So to one who doesn't have much experience with the SA code, I would think that somehow one of the numbers or aggregates are getting confused and getting turned into CLOBS somehow... (DatabaseError) ORA-00932: inconsistent datatypes: expected NUMBER got CLOB > > the last resort will be that we just need to add an isinstance() > check into convert_result_value to ensure that all LOBs get the read > () call and all strings do not. Hmmm, this appears to be a regression since .3.7 worked.... I'm assumming new CLOB code somewhere is overeager in converting to CLOBs..... You mentioned previously that this is an error on the coming back into SA side. I'm not sure how that is possible if the error is thrown on the cursor.execute. How will convert_result_value do anything if the error is coming from cxOracle before SA even has a result to look at? Thanks again for the response! -matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
