Stephan
Stephan
can we vote this issue up a bit ? Yugabyte is not usable when creeate/drop table operations can cause incosistent states for the database
The task just links back to this thread. The lack of this feature renders Yugabyte unusable for every projects that rely on automigrations
Great to hear, but it still does not work. I picked up on the good news and started a quick test : 1. firing up a yugabyte instance from docker...
Adding those flags (--ysql_yb_ddl_rollback_enabled,--report_ysql_ddl_txn_status_to_master,--ysql_ddl_transaction_wait_for_ddl_verification) made the script work. Thank you
No unfortunateley not, this missing feature renders yugabyte unusable for us sadly. We are waiting on it one day :)
is phase 3 still alive ?
Is that ever getting fixed ? just had the same problem hindering me to generate a Schema with bodies ..