ERD Logic needs refactoring

[lovelyjoy1991]

Problem

Currently, the frontend is sending back a big bundle of all the operations done in the frontend ERD Table. This ERD table object is divided by add, drop, and alter. All the add operations will execute first then drop, then alter. This logic was BAD.

Solution

Need redesign frontend to send back "sequental" operations instead of bundling operations by add, drop, alter. Because it takes care of multiple edge cases and users in the front can do as many operations they want to ensure SAVE works.
Previous team has illustrated the problem below. The current backend has been written out already. Next step, need to make sure the frontend is sending back the appropriate logic.

This is written at backend/src/ipcHandlers/dbCRUDHandlerERD.ts and will replace backend/src/ipcHandlers/dbCRUDHandler.ts when this is ready

Additional information

No response

👨‍👧‍👦 Contributing

• 🙋‍♂️ Yes, I'd love to make a PR to implement this feature!