Thanks Mike for your response.
It's more likely due to multi threading because this error is coming very
randomly, If this was due to permutations you mentioned then it should happen
every time which is not the case here.
Any recommendations for handling sessions in multithreading?
--
Thanks Mike for your reply.
We are using cx Oracle as driver
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post example code, please provide an MCVE: Minimal, Complete, and Verifiable
Example. See http://stackoverflow.com/help/mcve for a
One of my project is built around Django rest framework and Sqlalchemy as ORM.
This application is thread based so randomly we are seeing one of thread
transaction showing connection closed error.
Randomly when my application is trying to insert the record in table we are
seeing exception the
link to a documentation section that lists out all the
> possibilities can be added.
>
> On Sun, Aug 4, 2019, at 8:58 AM, Abhishek Sharma wrote:
>
> I am able to figure out the issue but still I am not sure what caused
> that, I moved the relationship from deal model to deal_term_r
I am able to figure out the issue but still I am not sure what caused that, I
moved the relationship from deal model to deal_term_rate_options model with
backref option and now I can see my table deal.deal in metadata, I am guessing
may be some circular dependency was there which may be causing
Thanks for information, my both the tables deal_term_rate_options and deal are
in different schema, deal_term_rate_options is in menu schema and deal table in
deal schema.
Do I still not required to set foreign key constraint like deal.deal.deal_id on
deal_term_rate_options table?
--
I am using SQLALCHEMY Version 1.2.17
I am using declarative approach to define models, One of my declarative
table definition not available in metadata even i attached the table with
metadata so when other table which is in same metadata is trying to create
relationship with that table it
Team can someone help us to resolve this issue.
I am not sure whether due to this issue my apache process got hanged and
need to restart to get response.
Please help us to troubleshoot this issue.
On Wed, Sep 30, 2015 at 9:49 PM, Abhishek Sharma <abhisharma8...@gmail.com>
wrote:
> Tea
ine 418, in do_close
[Wed Sep 30 03:03:48 2015] [error] dbapi_connection.close()
[Wed Sep 30 03:03:48 2015] [error] DatabaseError: ORA-25408: can not
safely replay call
Can someone help us to resolve this issue.
On Sat, Sep 26, 2015 at 10:28 AM, Abhishek Sharma <abhisharma8...@gmail
in sqlalchemy to handle this issue at DB connection level
while making DB connection.
Thanks
Abhishek Sharma
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
that object in session to update the DB and
there is no commit but sqlalchemy emitting update query on DB.
On 18-Aug-2015 8:46 PM, Mike Bayer mike...@zzzcomputing.com wrote:
On 8/18/15 6:31 AM, Abhishek Sharma wrote:
Hi Mike,
I am attaching the Code and Model Info in which I am
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
', Unicode(length=100), primary_key=False),
Do I need to call all or first method on query object to get Unicode object
rather than str object.
Thanks
Abhishek Sharma
On Tue, Aug 11, 2015 at 2:22 PM, Mike Bayer mike...@zzzcomputing.com
wrote:
On 8/11/15 1:58 PM, Abhishek Sharma wrote:
Hi Team
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
steps?
SQLAlchemy Version: 0.9.9
We are using classic mapping for attributes mapping with DB columns.
On Tue, Aug 4, 2015 at 3:49 PM, Mike Bayer mike...@zzzcomputing.com wrote:
On 8/4/15 1:41 PM, Abhishek Sharma wrote:
is this followings two instructions compulsory while defining new
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
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
versus this test case.
On 8/5/15 11:45 AM, Abhishek Sharma wrote:
that object already got saved in DB after
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
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 types for cx_oracle are
organized
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
of using non ascii data?
On Thu, Jul 30, 2015 at 2:55 AM, Mike Bayer mike...@zzzcomputing.com
wrote:
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
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
22 matches
Mail list logo
