sqlalchemy.engine.default.DefaultExecutionContext

Return a new cursor generated from this ExecutionContext's connection.

Some dialects may wish to change the behavior of connection.cursor(), such as postgresql which may return a PG "server side" cursor.

Return a dictionary of parameters applied to the current row.

This method can only be used in the context of a user-defined default generation function, e.g. as described at :ref:`context_default_functions`. When invoked, a dictionary is returned which includes entries for each column/value pair that is part of the INSERT or UPDATE statement. The keys of the dictionary will be the key value of each _schema.Column, which is usually synonymous with the name.

return self.cursor.lastrowid, or equivalent, after an INSERT.

This may involve calling special cursor functions, issuing a new SELECT on the cursor (or a new one), or returning a stored value that was calculated within post_exec().

This function will only be called for dialects which support "implicit" primary key generation, keep preexecute_autoincrement_sequences set to False, and when no explicit id value was bound to the statement.

The function is called once for an INSERT statement that would need to return the last inserted primary key for those dialects that make use of the lastrowid concept. In these cases, it is called directly after .ExecutionContext.post_exec.

Return a sequence of OUT parameter values from a cursor.

For dialects that support OUT parameters, this method will be called when there is a .SQLCompiler object which has the .SQLCompiler.has_out_parameters flag set. This flag in turn will be set to True if the statement itself has .BindParameter objects that have the .isoutparam flag set which are consumed by the .SQLCompiler.visit_bindparam method. If the dialect compiler produces .BindParameter objects with .isoutparam set which are not handled by .SQLCompiler.visit_bindparam, it should set this flag explicitly.

The list of names that were rendered for each bound parameter is passed to the method. The method should then return a sequence of values corresponding to the list of parameter objects. Unlike in previous SQLAlchemy versions, the values can be the raw values from the DBAPI; the execution context will apply the appropriate type handler based on what's present in self.compiled.binds and update the values. The processed dictionary will then be made available via the .out_parameters collection on the result object. Note that SQLAlchemy 1.4 has multiple kinds of result object as part of the 2.0 transition.

Return a 'result processor' for a given type as present in cursor.description.

This has a default implementation that dialects can override for context-sensitive result type handling.

Called after the execution of a compiled statement.

If a compiled statement was passed to this ExecutionContext, the last_insert_ids, last_inserted_params, etc. datamembers should be available after this method completes.

Called before an execution of a compiled statement.

If a compiled statement was passed to this ExecutionContext, the statement and parameters datamembers must be initialized after this statement is complete.