Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-26 Thread Simon King
On Tue, Aug 25, 2015 at 6:43 PM, Abhishek Sharma abhisharma8...@gmail.com wrote: Hi Team, We are executing select query using self.session.query(Model).filter(filter_conditions).first() Then we are storing the about query result in result variable. Then we are trying to

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-25 Thread Abhishek Sharma
Hi Team, We are executing select query using self.session.query(Model).filter(filter_conditions).first() Then we are storing the about query result in result variable. Then we are trying to update one of model attribute like result.description=value Even though we have not added

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-12 Thread Abhishek Sharma
I am using session.query(Model).filter(conditions) but still getting UnicodeErrors On Wed, Aug 12, 2015 at 10:07 AM, Mike Bayer mike...@zzzcomputing.com wrote: On 8/12/15 9:55 AM, Abhishek Sharma wrote: Hi Team, We are not calling all or first method on got query object. We

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-12 Thread Abhishek Sharma
Hi Team, We are not calling all or first method on got query object. We are just passing query object to set method of python and we are getting Unicode Error ASCII CODEC Can not decode this means I am not getting Unicode Object from SQLAlchemy side. Column('dlrprod_name_pri',

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-11 Thread Mike Bayer
On 8/11/15 1:58 PM, Abhishek Sharma wrote: Hi Team, With asynchronous request my model object Unicode type column not returning Unicode object but if I do same action using synchronous I am getting Unicode object SQLAlchemy has no asynchrnous API itself so this has to do

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-11 Thread Abhishek Sharma
Hi Team, With asynchronous request my model object Unicode type column not returning Unicode object but if I do same action using synchronous I am getting Unicode object On 05-Aug-2015 11:43 PM, Abhishek Sharma abhisharma8...@gmail.com wrote: thanks for your help. its seems to

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-05 Thread Abhishek Sharma
Hi Team, I have created customized data type using TypeDecorator approach. *from sqlalchemy import TypeDecorator, CLOB* *class ForceUnicodeClob(TypeDecorator): impl = CLOB* * def process_bind_param(self, value, dialect): if isinstance(value, str):value =

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-05 Thread Mike Bayer
On 8/5/15 9:24 AM, Abhishek Sharma wrote: Hi Team, I have created customized data type using TypeDecorator approach. *from sqlalchemy import TypeDecorator, CLOB* *class ForceUnicodeClob(TypeDecorator): impl = CLOB* * def process_bind_param(self, value, dialect): if

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-05 Thread Abhishek Sharma
that object already got saved in DB after session.commit(). After that i am retrieving object which already stored in db. still same issue. On Wed, Aug 5, 2015 at 7:41 PM, Mike Bayer mike...@zzzcomputing.com wrote: On 8/5/15 9:24 AM, Abhishek Sharma wrote: Hi Team, I have created

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-05 Thread Mike Bayer
Attached is a test script illustrating the code you have below along with a round trip verification using a simple Model class mapped to the table. Please confirm this script works as expected, as it does here. Assuming that works, determine what's different about your real-world environment

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-05 Thread Abhishek Sharma
thanks for your help. its seems to be working. i will troubleshoot in my development environment. On Wed, Aug 5, 2015 at 10:37 PM, Mike Bayer mike...@zzzcomputing.com wrote: Attached is a test script illustrating the code you have below along with a round trip verification using a simple Model

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-04 Thread Abhishek Sharma
applying convert_unicode to CLOB type does not have any effect. Still I am getting str type object from sqlalchemy for CLOB type column On Mon, Aug 3, 2015 at 1:27 PM, Mike Bayer mike...@zzzcomputing.com wrote: On 8/3/15 1:04 PM, Abhishek Sharma wrote: what about CLOB type? Unicode only

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-04 Thread Mike Bayer
On 8/4/15 11:29 AM, Mike Bayer wrote: On 8/4/15 7:41 AM, Abhishek Sharma wrote: in case lot of overhead will be there so it is better to use that column label only well it doesn't work anyway because data from a CLOB is not in cx_oracle's world a String, it's a LOB. The CLOB / NCLOB

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-04 Thread Mike Bayer
On 8/4/15 7:41 AM, Abhishek Sharma wrote: in case lot of overhead will be there so it is better to use that column label only well it doesn't work anyway because data from a CLOB is not in cx_oracle's world a String, it's a LOB. The CLOB / NCLOB types for cx_oracle are organized in their

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-04 Thread Abhishek Sharma
is this followings two instructions compulsory while defining new type? m.drop_all(e) m.create_all(e) this instructions are not feasible , because DB team already defined schema and normal user can not drop and create table. On Tue, Aug 4, 2015 at 8:59 PM, Mike Bayer mike...@zzzcomputing.com

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-04 Thread Mike Bayer
On 8/4/15 1:41 PM, Abhishek Sharma wrote: is this followings two instructions compulsory while defining new type? m.drop_all(e) m.create_all(e) no that is just part of the demonstration script. this instructions are not feasible , because DB team already defined schema and normal user

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-03 Thread Abhishek Sharma
what about CLOB type? Unicode only handles String type. Do i need to use convert_unicode there? On Mon, Aug 3, 2015 at 6:56 PM, Mike Bayer mike...@zzzcomputing.com wrote: On 8/1/15 12:12 PM, Abhishek Sharma wrote: Thanks for help. But still i have confusion over encoding and decoding

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-03 Thread Mike Bayer
On 8/3/15 1:04 PM, Abhishek Sharma wrote: what about CLOB type? Unicode only handles String type. Do i need to use convert_unicode there? if your CLOB expects non-ascii characters then yes. though on Oracle I thought you really need to be using NCLOB for a col that stores unicode. On

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-03 Thread Mike Bayer
On 8/1/15 12:12 PM, Abhishek Sharma wrote: Thanks for help. But still i have confusion over encoding and decoding procedure which will take place before retrieving and storing the results in DB. In case if i am not using convert_unicode option and data type is String so python process will

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-08-01 Thread Abhishek Sharma
Thanks for help. But still i have confusion over encoding and decoding procedure which will take place before retrieving and storing the results in DB. In case if i am not using convert_unicode option and data type is String so python process will give str object to sqlalchemy at the time of

[sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-07-29 Thread Abhishek Sharma
We are using sqlalchemy version 0.7, python 2.7 and oracle Database. We have ASCII as default python encoding and DB have ISO-8052 encoding. Our DB tables contains some of characters which are out of ASCII range. So when we are running query on those tables we are getting Unicode Decode error

Re: [sqlalchemy] UnicodeDecode error on sqlalchemy select query

2015-07-29 Thread Mike Bayer
On 7/29/15 2:23 PM, Abhishek Sharma wrote: We are using sqlalchemy version 0.7, python 2.7 and oracle Database. We have ASCII as default python encoding and DB have ISO-8052 encoding. Our DB tables contains some of characters which are out of ASCII range. So when we are running query on