mike bayer writes:
> On 02/14/2017 11:02 AM, Manuel wrote:
>> Thanks, I'm still in the early stages of this project and any comments
>> are highly appreciated. What I'm trying to actually accomplish is to
>> build some complex queries to be executed against an Odoo [1] DB. Odoo
>> has it's own
On 02/14/2017 11:02 AM, Manuel wrote:
mike bayer writes:
it's sort of a bug but you're attempting to do a thing that in any case is not
possible. The "mock" execution strategy does not support operations that
require result sets, because it isn't actually querying a database. If we
add the
mike bayer writes:
> it's sort of a bug but you're attempting to do a thing that in any case is not
> possible. The "mock" execution strategy does not support operations that
> require result sets, because it isn't actually querying a database. If we
> add the "run_callable" method onto the Moc
On 02/14/2017 09:53 AM, Manuel Vázquez Acosta wrote:
Hi,
I'm assessing how to use SA within another project that uses psycopg2
and maintains it's connection pool and the like.
I have the following code:
@property
def table(self):
from sqlalchemy import create_engine
f
Hi,
I'm assessing how to use SA within another project that uses psycopg2 and
maintains it's connection pool and the like.
I have the following code:
@property
def table(self):
from sqlalchemy import create_engine
from sqlalchemy.schema import Table
table = self.
