New answers tagged mysql-workbench
I had the same problem and I found the missing dll in C:\Windows\SysWOW64 folder. Just copy it to System32 and was fixed. If you still have the @MikeW error with python.exe is because you have a 32bits version of one and the 64bits of the other (Python and Workbench).
If You already use MySQL Workbench, You can use menu: Database -> Synchronise with any Source Before apply changes it show You script, which You can copy and if need edit You can test it on copy of databases Also there are many other tools: Navicat SQLyog dbSchema and etc example of script: ALTER TABLE `test_db`.`company1_name` ADD FULLTEXT INDEX ...
Have you looked at Edit -> Preferences -> SQL Editor -> Query Editor? There are a couple of "beautifier" and "capitalise" options there.
mysql_upgrade is a shell script and does not have a GUI interface from MySQL Workbench. Run it from the command line (depending on your operating system).
Using MySQL Workbench you can reverse engineer a database into an EER model. See the documentation for details. For a visual representation (EER diagram) of this schema, select Model, Create Diagram from Catalog Objects to create the EER Diagram for the model. There are binaries available or a PPA depending on your version of ubuntu. See here for ...
This is a case of what's called "generalization/specialization" in ER lingo. It's really the same thing as what object models call "superclass/subclass" as you have done. There are two separable issues. The first is how do you want to draw the diagram, and the second is how do you want to design the tables. As far as drawing the diagram goes, I would ...
No, MySQL Workbench doesn't lock your database for read or write.
EDIT: I guess I deserved the -1 for my brevity and incomplete (i.e. wrong) answer. I was on the phone and had to keep it quick. Let me try again. I did a dry run for you on two test servers using the MySQL Workbench 6.3 CE migration wizard. With the default options the migration is -non- locking. This vanilla method has a downside however. If you migrate ...
The EER diagram is correct. There should be no relationships because WordPress does not have any constraints. The EER diagram shown in the codex is only for reference (it's a dummy EER diagram). You must rely on other logical operations to make sure you have no orphaned data. Source: https://codex.wordpress.org/Database_Description Please note that ...
I'm fairly certain the MySQL not only has users listed by name and password, but also by "where they are coming from". You may want to check and make sure the user is listed as being allowed to connect from "localhost".
Top 50 recent answers are included