Need help with generating Unique constraints in the declarative models.

[Vrushank-21]

CREATE TABLE "DUMMY" (
	"attr1"	integer NOT NULL,
	"attr2"	char NOT NULL,
	"attr3"	datetime NOT NULL,
	CONSTRAINT "pk1" PRIMARY KEY("attr1","attr3"),
	CONSTRAINT "uk" UNIQUE("attr1","attr2","attr3")
);

For the above table, what I want is

class DUMMY(Base):
    __tablename__ = 'DUMMY'
    __table_args__ = (
        PrimaryKeyConstraint('attr3', name='pk1'),
        UniqueConstraint('attr1', 'attr2', 'attr3', name='uk')
    )

    attr1 = Column(Integer, nullable=False)
    attr2 = Column(CHAR, nullable=False)
    attr3 = Column(DateTime)

But this is what I get:

class DUMMY(Base):
    __tablename__ = 'DUMMY'
    __table_args__ = (
        UniqueConstraint('attr1', 'attr2', 'attr3', name='uk'),
    )

    attr1 = Column(Integer, primary_key=True, nullable=False)
    attr2 = Column(CHAR, nullable=False)
    attr3 = Column(DateTime, primary_key=True, nullable=False)

[agronholm]

What's the problem with the generated code?

[Vrushank-21]

Your SQL specifies a two-column primary key constraint, but your desired code only has a single column in the PK constraint. Why would you want sqlacodegen to generate the wrong code?

Sincere apologies with the wrong DDL. The second primary key was an edit I made before copy-pasting here. The results I mentioned were for the case of 1 primary key only

[agronholm]

So what is it that you want then? Clearly the unique constraint is not the issue here (contrary to what the topic says).

[Vrushank-21]

Sorry about the bad explanation on my part. I honestly wish I could explain it properly.

So yesterday, when I had raised an issue, you asked me try running sqlacodegen on a test.sqlite3 file. It worked exactly the way I wanted. But when I used the same DDL to create the exact same database locally and ran sqlacodegen, the final code generated was slightly different from the one obtained from your file 'test.sqlite3'. And the result I obtained is the one I had mentioned above.

All I wanted to know was why this difference showed up and why was I not getting the same code you were getting.

[agronholm]

The only reason why sqlacodegen would generate an explicit PrimaryKeyConstraint would be if it had an explicit name that wasn't what would be generated by default. Does this answer your question?

[Vrushank-21]

Yes. Got it . Thank you.