On Wednesday, October 3, 2018 at 9:40:37 AM UTC-4, Mike Bayer wrote:
>
>
> those are not going to change within 1.2 or 1.3 but it's not ideal to
> be relying on them. For query._entities, you can use the public
> accessor query.column_descriptions. for _with_options I'm not sure
> what it
The insert is by itself not a RETURNING and doesn't return any rows.
The actual exception raised is:
sqlalchemy.exc.ResourceClosedError: This result object does not return
rows. It has been closed automatically.
and you'll get this just if you run the insert by itself:
returning_query =
Ok, you're gonna have to give me a pointer or two to where the aliasing is
actually happening internally to get this done. I've poked and prodded the
source, but I can't find where the aliasing *actually* happens.
I'm assuming it's in *strategies.py*, and *_generate_row_adapter*, but I
can't
I would look to generalize the whole thing, e.g. auto-generate the
*Metacontent class, as well as the association proxy (like a
HasMetacontent mixin for Item), the assoc proxy can be genericized
starting like this:
class Item(Base):
__tablename__ = 'item'
id = Column(Integer,
On Tue, Oct 2, 2018 at 4:44 PM Jonathan Vanasco wrote:
>
> And a quick followup to Michael:
>
> I didn't want to pollute the comments in
> https://bitbucket.org/zzzeek/sqlalchemy/issues/3225/query-heuristic-inspection-system
> as there may not have been any substantial changes and I'm just
Hello,
I use the recipe for explain as described
(https://bitbucket.org/zzzeek/sqlalchemy/wiki/UsageRecipes/Explain), which
does the job completely for select statements (I have no idea how it works
however :p) in version 1.2.11
The recipe at the moment is
from sqlalchemy import *
from
