[sqlalchemy] Column vs Table constraints for Column(unique=True) in Postgres

[rob]

Is there a way to control whether DDL emitted by SQLAlchemy uses a column 
and/or table constraint for uniqueness?

It seems the following 
class Part(Base):
    __tablename__ = 'part'
    third_party_id = Column(Integer, nullable=True, default=None, unique=
True)


emits a table constraint
CREATE TABLE part (
    third_party_id INTEGER, 
    CONSTRAINT uq_part_third_party_id UNIQUE (third_party_id)
)




Is it possible to emit the following with a column constraint instead?
CREATE TABLE part (
    third_party_id INTEGER CONSTRAINT uq_part_third_party_id UNIQUE
)

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.