SQL Check warnings for non-transactional statements i migrations
artman opened this issue · comments
Is your feature request related to a problem?
When generating migrations with statements that can't be run in a transaction (e.g. CREAT INDEX CONCURRENTLY), Bytebase re-arranges those statements and runs them outside of the transaction. This is a potentially dangerous operation and should have warnings associated with it.
Describe the solution you'd like
The regular SQL check should generate warnings for these statements so that the engineer it aware that the statements will be re-arranged.
Additional context
No response
