sqlalchemy sqlalchemy Blue-sky Discussions
Blue Sky Discussions
Things that SQLAlchemy may want to implement someday. For SQLAlchemy maintainers use
-
You must be logged in to vote Views as schema objects that can be created and dropped
low priority feature schemathings related to the DDL related objects like Table, Column, CreateIndex, etc. -
You must be logged in to vote coalesce() incorrectly returns type T | None when coalescing T | None with T
quagmirereally hard to make the issue work "correctly" without lots of complication, risk typingpep -484 typing issues. independent of "mypy" awaiting pepthere's no PEP to do what we want to do -
You must be logged in to vote -
You must be logged in to vote Copy instruction (for massive, bulk load) support
use casenot really a feature or a bug; can be support for new DB features or user use cases not anticipated dmlINSERT, UPDATE, DELETE, often with ORM -
You must be logged in to vote -
You must be logged in to vote Support for temporal table queries?
mysql sql use casenot really a feature or a bug; can be support for new DB features or user use cases not anticipated temporal table modifiersa more requsted feature code review in progresscode has been provided that's in review as PR and/or gerrit -
You must be logged in to vote Support MERGE statement
sql use casenot really a feature or a bug; can be support for new DB features or user use cases not anticipated -
You must be logged in to vote add translate_polymorphic_identity event hook for on-the-fly polymorphic loading, handling of missing identities
feature orm inheritanceissues to do wtih ORM inheritance, a particularly tricky area -
You must be logged in to vote Postgresql supports fetching tuples
postgresql use casenot really a feature or a bug; can be support for new DB features or user use cases not anticipated -
You must be logged in to vote have math operators + and - do something reasonable for dates and timedeltas (or raise)
sql use casenot really a feature or a bug; can be support for new DB features or user use cases not anticipated -
You must be logged in to vote allow optimized compare to receive a CTE
orm performancewhere performance can be improved. add "bug" only if it's a performance degradation use casenot really a feature or a bug; can be support for new DB features or user use cases not anticipated -
You must be logged in to vote -
You must be logged in to vote reflect PG custom types besides ENUM / support composite types
postgresql feature reflectionreflection of tables, columns, constraints, defaults, sequences, views, everything else datatypesthings to do with database types, like VARCHAR and others -
You must be logged in to vote dialect itself should create a cache key? / spread a single statement cache over multiple engines
sql use casenot really a feature or a bug; can be support for new DB features or user use cases not anticipated statement caching -
You must be logged in to vote Reflect exclude constraints from Postgres tables.
postgresql feature reflectionreflection of tables, columns, constraints, defaults, sequences, views, everything else