sql: schema updates have problematic shortcomings #13804
Labels
A-sql-semantics
S-3-ux-surprise
Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
Milestone
This is a meta issue that aims to collect and structure the various UX issues around schema changes.
Issues arising from performing schema updates inside a transaction:
Issues in our use of table leases:
Issues arising from asynchronous schema updates outside of a transaction:
Can't use table descriptors while async change is ongoing (improper locking in leasemgr?)
Can't use table name after it's been dropped:
Other/misc
Improper handling of schema change semantics:
DROP INDEX...RESTRICT
fails to prevent dropping indexes with dependent constraints sql:DROP INDEX...RESTRICT
fails to prevent dropping indexes with dependent constraints #12620Slightly related wishlist, listed here for reference but not targeted by the meta-issue
cc @vivekmenezes
The text was updated successfully, but these errors were encountered: