Is it safe, from within either the 'before_execute' or
'before_cursor_execute' events, to use the same connection to execute a SQL
statement before the current one? I assume there is a good chance the
answer is no, at least for before_cursor_execute.
Why? I only want to issue the SQL to
Perfect, thanks much!
On Saturday, March 7, 2015 at 6:38:08 PM UTC-5, Michael Bayer wrote:
Kent jkent...@gmail.com javascript: wrote:
I'm implementing database session variables (in Oracle,
DBMS_SESSION.SET_CONTEXT(...)), in order to be able to set (from
sqlalchemy) and retrieve (from
Kent jkentbo...@gmail.com wrote:
Is it safe, from within either the 'before_execute' or
'before_cursor_execute' events, to use the same connection to execute a SQL
statement before the current one? I assume there is a good chance the answer
is no, at least for before_cursor_execute.
if
Hi there,
I was wondering if it was possible to have an attribute on a model that is
proxied through a relationship in a many-to-one case. I know for M2M there
is association_proxy, but that does not seem to work.
Example time!
class Show(Base):
id = sqlalchemy.Column(sqlalchemy.Integer,
What version of SqlAlchemy are you using, and what error are you seeing?
I use the association_proxy for M2M, M2O, O2O all the time.
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To unsubscribe from this group and stop receiving emails from
