subqueryload isn't caching

not sure what is happening here, but two things to note:

1. the subqueryload never caches, period. not sure if this is dependent on being from the lazy loader or not.
2. it is using the lazy loader’s cache, which seems a little strange

Running this with -Werror hits the size alert for the A.b lazyloader.

from sqlalchemy import Column
from sqlalchemy import create_engine
from sqlalchemy import ForeignKey
from sqlalchemy import Integer
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy.orm import declarative_base
from sqlalchemy.orm import relationship
from sqlalchemy.orm import Session

Base = declarative_base()


class A(Base):
    __tablename__ = "a"

    id = Column(Integer, primary_key=True)
    b_id = Column(ForeignKey("b.id"))
    b = relationship("B")


class B(Base):
    __tablename__ = "b"
    id = Column(Integer, primary_key=True)
    c1 = relationship("C1", lazy="subquery")


class C1(Base):
    __tablename__ = "c1"
    id = Column(Integer, primary_key=True)
    b_id = Column(ForeignKey("b.id"))


e = create_engine("sqlite://", echo=True)
Base.metadata.create_all(e)

s = Session(e)

s.add(
    A(
        b=B(
            c1=[C1()],
        )
    )
)
s.commit()


def go():
    s.close()
    a1 = s.query(A).first()
    a1.b


for i in range(50):
    go()

[zzzeek]

well im going to remove the warning from the loader strategies altogether so the warning won’t be seen anymore. for the main cache, im not sure what we’d do with a dump of 700 items, so while ther are some debugging features on cachekey im not sure about the dump feature.

[CaselIT]

@zzzeek do you think it may be worth it to merge that change, so it’s easier to debug cache issues?