Awesome! Thanks!
-Lyla
On Mon, Apr 29, 2019 at 1:55 PM Mike Bayer wrote:
> On Mon, Apr 29, 2019 at 1:37 PM Lyla Fischer wrote:
> >
> > Ah. I think that I have been thinking of a session as a cache instead of
> a transaction, which is incorrect. (It's similar because you hav
e.
Totally wrong abstraction, sorry.
-Lyla
On Mon, Apr 29, 2019 at 1:04 PM Mike Bayer wrote:
> On Mon, Apr 29, 2019 at 12:04 PM Lyla Fischer wrote:
> >
> > Sorry about the language. I'll try to stick to "intuitive" and
> "surprising" in the future.
> >
or its
foreign key", while the reverse didn't occur to me.
-Lyla
On Mon, Apr 29, 2019 at 11:14 AM Mike Bayer
wrote:
> On Mon, Apr 29, 2019 at 7:22 AM Lyla Fischer wrote:
> >
> > If I can comment on what seems instinctive to someone who just recently
> read the documentati
If I can comment on what seems instinctive to someone who just recently
read the documentation, and made assumptions based off of it: My
understanding was that the relationship abstractions were supposed to be
about making foreign keys easier to keep track of, and being able to go
both ways on a
eclarative_base()
> >> > > Base.query = db_session.query_property()
> >> > >
> >> > > class Head(Base):
> >> > > __tablename__ = 'head'
> >> > > id = Column(String, primary_key=True)
> >> &
