Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8151981
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 6, 20262026-06-06T15:34:25+00:00 2026-06-06T15:34:25+00:00

I have an SQLAlchemy model like the one below, and at first it didn’t

  • 0

I have an SQLAlchemy model like the one below, and at first it didn’t work (problems with the join, and then expecting a scalar instead of a list). I “fixed” it in the included version, but I really can’t understand why it behaved like that.

At first I expected that with those ForeignKeys the Sizes.items relationship() shouldn’t need an explicit primaryjoin, and when I added it SA started expecting a scalar and I had to explicitly specify uselist=True.

Why doesn’t the relationship automatically detect one or both those things?

class Category(Base):
    __tablename__ = 'categories'
    pk   = Column(String(6), primary_key=True)

class Item(Base):
    __tablename__ = 'items'
    pk          = Column(String(6), primary_key=True)
    category_pk = Column(String(6), ForeignKey('categories.pk') )
    size        = Column(Integer(), nullable=False)
    category    = relationship('Category', backref=backref('items'))

class Sizes(Base):
    __tablename__ = 'sizes'
    category_pk = Column(String(6), ForeignKey('categories.pk'),
                    ForeignKey('items.category_pk'), primary_key=True )
    size        = Column(Integer(), ForeignKey('items.size'), primary_key=True )
    category    = relationship('Category', backref=backref('sizes'))
    items       = relationship('Item',
        uselist=True,
        primaryjoin="and_(Sizes.category_pk==Item.category_pk, Sizes.size==Item.size)" )
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-06T15:34:26+00:00Added an answer on June 6, 2026 at 3:34 pm

    I believe what is happening is that you have two foreign keys, not a single FK on two columns. It works a bit different the primary_key=True where you can do that.

    Try something like:

    class Category(Base):
        __tablename__ = 'categories'
        pk   = Column(String(6), primary_key=True)
    
    class Item(Base):
        __tablename__ = 'items'
        pk          = Column(String(6), primary_key=True)
        category_pk = Column(String(6), ForeignKey('categories.pk') )
        size        = Column(Integer(), nullable=False)
        category    = relationship('Category', backref=backref('items'))
    
    class Sizes(Base):
        __tablename__ = 'sizes'
        category_pk = Column(String(6), primary_key=True )
        size        = Column(Integer(), primary_key=True )
        category    = relationship('Category', backref=backref('sizes'))
        items       = relationship('Item')
    
        __table_args__ = (
            ForeignKeyConstraint(
                ["category_pk", "size"],
                ["items.category_pk", "items.size"]
            ),
        )
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I got a simple problem in SQLAlchemy. I have one model in a table,
To provide an activity log in my SQLAlchemy-based app, I have a model like
Say I have a SqlAlchemy model something like this: from sqlalchemy.ext.declarative import declarative_base from
I have a SQLAlchemy model with a one-to-many relationship between table x and table
I have a SQLAlchemy model set up in my application that should mimic the
I've got a sqlalchemy model that is set up like this: class Entry(Base): __tablename__
I have this to SQLAlchemy(using the Flask SqlAlchemy) objects defined: class User(db.Model): id =
I have the following model classes declared by SQLAlchemy: class User(Base): id = Column(Integer,
I'd like to have sqlalchemy get the hostname, username, and password for the mysql
I have a declarative SQLAlchemy object with deferred columns, declared like this: class Review(Base):

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.