Hi! Do you recommend building ERDs in MySQL Workbench on professional settings? Or would you recommend better platforms for production level ERDS. Thank you!
Good question. MySQL workbench is handy because you can generate it directly from the database, making it easier to check that it matches the tables. I usually use different tools only because that’s what the rest of the company does.
in more professional tone. It seems the document provided is a Data Structure Diagram (DSD), which typically offers a visual depiction of the data structure and its relationships. However, an Entity-Relationship Diagram (ERD) would be more appropriate for detailing relationships, including many-to-many relationships. In an ERD, relationships are explicitly defined, and many-to-many relationships are typically represented using associative tables to establish the connection between entities
@@DatabaseStar You are too nice to jerks like me my good sir or should i say Dag. i hope you have a great day and a great morning as well, in which you had a nice smashed avo in a toast for brekkie with your top notch Sheila in your budgie smugglers and if you are having brekkie in your budgie smugglers with your top notch Sheila you are a root rat in my book. you are making us Dags feel jealous.
When I load an existing db, only the selected tables are plottet but not the relationships (lines). It's not possible that in an existing db no foreign keys have been defined, is it?
Yeah it is possible that a database has no foreign keys. It’s not mandatory, but it’s recommended. So if there are no foreign keys then there would not be any lines on the diagram.
@@DatabaseStar You are too nice to jerks like me my good sir or should i say Dag. i hope you have a great day and a great morning as well, in which you had a nice smashed avo in a toast for brekkie with your top notch Sheila in your budgie smugglers and if you are having brekkie in your budgie smugglers with your top notch Sheila you are a root rat in my book. you are making us Dags feel jealous.
Same thing happens with me. Tried multiple different versions, different machines, db in docker/bare metal.... It used to work before my schema got big, so thinking it has something to do with that. Did you ever figure out a solution?