Re: [sqlalchemy] How does latest sqlalchemy pickle a column?

> This is what I get in SQLAlchemy > > > {'calculateTaxesByID': {('totalPriceEx()',): {}}, 'averageCost': {None: > Decimal('7.4838709677419355')}, 'totalPriceEx': {None: Decimal('17.50')}, > 'getBasePriceEx': {None: Decimal('17.50')}} > > This is the result when I rand the following code in P

[sqlalchemy] How does latest sqlalchemy pickle a column?

hi, We recently upgraded from SQLAlchemy to 0.4.8 to 0.9.3 also we upgrade psycopg2 etc and we are using postgresql 9.2 We run in a very strange problem that the unpickle of one of the columns is giving different result when we do this in a python procedure call. When I run in the in the orm w

Re: [sqlalchemy] after_cursor_execute question

Wonderful. Everything I found referenced to a `statement` or `stmt` was either a non-dialect compiled version (just turning a query into a string via `print`, `str()`, etc), or explicitly passing a dialect into the compile function. -- You received this message because you are subscribed t

Re: [sqlalchemy] after_cursor_execute question

that’s the string we just sent to the DBAPI cursor. we don’t make any other kind of string representation of it. > On Oct 17, 2014, at 4:09 PM, Jonathan Vanasco wrote: > > the docs just say: > (http://docs.sqlalchemy.org/en/latest/core/events.html#sqlalchemy.events.ConnectionEvents.after_

[sqlalchemy] after_cursor_execute question

the docs just say: (http://docs.sqlalchemy.org/en/latest/core/events.html#sqlalchemy.events.ConnectionEvents.after_cursor_execute) - *statement* – s

Re: [sqlalchemy] SAWarnings when using history_meta.py versioning and Inheritance.

> On Oct 17, 2014, at 3:50 PM, JPLaverdure wrote: > > Hi Michael, > > My bad, they do indeed only show up on mapping... which takes place when my > pyramid app instantiates. Sorry for the confusion :) > Still, they could be unnerving for someone deploying the app. Any way to not > have these

[sqlalchemy] Re: SAWarnings when using history_meta.py versioning and Inheritance.

Hi Michael, My bad, they do indeed only show up on mapping... which takes place when my pyramid app instantiates. Sorry for the confusion :) Still, they could be unnerving for someone deploying the app. Any way to not have these show up ? I did look into version_meta.py and tried to make some tw

Re: [sqlalchemy] SAWarnings when using history_meta.py versioning and Inheritance.

On 10/17/2014 02:52 PM, JPLaverdure wrote: > Hello, > > It seems a number of SAWarnings are being thrown whenever I > instantiate Versioned objects which make use of inheritance: > > | > SAWarning:Implicitlycombining column container_history.changed > withcolumn barcoded_container_history.changed

[sqlalchemy] SAWarnings when using history_meta.py versioning and Inheritance.

Hello, It seems a number of SAWarnings are being thrown whenever I instantiate Versioned objects which make use of inheritance: SAWarning: Implicitly combining column container_history.changed with column barcoded_container_history.changed under attribute 'changed'. Please configure one or mo

Re: [sqlalchemy] Multi-AZ RDS on AWS, failover and SQLAlchemy

On Oct 17, 2014, at 4:47 AM, Jonas Oscarsson wrote: > Hi, > > We are running SQLAlchemy with a Multi-AZ Postgres RDS database on AWS and > are having trouble with database connections that hangs when failover occurs. > According to Amazon documentation for Multi-AZ RDS: > > When operations s

[sqlalchemy] Re: Multi-AZ RDS on AWS, failover and SQLAlchemy

Have you tried a Pessimistic Disconnect strategy? http://docs.sqlalchemy.org/en/latest/core/pooling.html#dealing-with-disconnects -- 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, s

[sqlalchemy] Re: Sqlalchemy and pickling data in a column with Postgresql?

hi, after further investigating this didn't turn out to be the issue. ORM code was adding the extra keys in the dictionary. you can consider the issue closed, sorry for the noise. marc On Friday, October 17, 2014 12:11:05 AM UTC-4, Marc Van Olmen wrote: > > Second attempt because Google Group

[sqlalchemy] Multi-AZ RDS on AWS, failover and SQLAlchemy

Hi, We are running SQLAlchemy with a Multi-AZ Postgres RDS database on AWS and are having trouble with database connections that hangs when failover occurs. According to Amazon documentation for Multi-AZ RDS: When operations such as DB Instance scaling or system upgrades like OS > patching are