MySQL doesn’t come pre-loaded with macOS Sierra and needs to be dowloaded from the MySQL site. The macOS Sierra Public Beta’s didn’t play well with MySQL 5.7.x, but these issues are now resolved by using MySQL 5.7.16
Mysql for mac os x 10.7 install#
Install PyMySQL=> sudo pip install PyMySQL Terminal command to check whether installed or not => pip3 list Install PyMySQL=> sudo easy_install-3.7 pymysql I've racked my brain, searched Google, read Stack Overflow, and spent hours trying to figure this out to no avail. If it helps I am officially running, Mac OS X 10.7.5, and I do have MAMP installed (is that an issue?)Īlso, the other day when I was trying all of this for the first time I installed (reinstalled?) MySQL, so I'm really in a tough spot at this point.
Mysql for mac os x 10.7 code#
Well, I've continually run the aforementioned code expecting a different result, so I'm not to far away from going insane.Īt this point in my Python career, I am new to this, but I am willing to try pretty much anything to get this up and running. Google/Stack Overflow that, and I am told to download a GCC package which I did the other day, 200 MB's or there-abouts and still no fix.Īt this point I am lost, they say insanity is doing the same thing over and over while expecting a different result. Setup script exited with error: command 'llvm-gcc-4.2' failed with exit status 1 Then I rerun my sudo code: sudo easy_install MySQL-python
Mysql for mac os x 10.7 how to#
If I find an original bug report, I'll mark this as a duplicate, but confirming in the meantime.Īlso, there is a workaround : you can use the native mysql connector instead of ODBC, which does have the added advantage of not suffering from the object limitations of the ODBC driver.Long story short, when I write the following: sudo easy_install MySQL-pythonĪll right, so there are plenty of threads and the like on how to fix that, so I run this code: export PATH=$PATH:/usr/local/mysql/bin I can confirm the buggy behaviour, it is not new to 3.5 though, it has been around since we first released LO, although I can't remember now if I opened a bug report at the time (nobody seems to care much for mysql connection problems, what with the past history, with it being Oracle and all that - unfortunate, but true). Is this a known bug? Is it related to the connector? Any known solution? In fact, when clicking on "Refresh Tables" I can see the server responds with the names of the existing tables in the database, but still they do not show up on LibreOffice.įind attached the screenshot and the network dump, all compressed in a zip file. I've sniffed the network traffic while testing the connection and while clicking on the "View"->"Refresh Tables" option and I can see MySQL queries going back and forth. I attach an screenshot with the successful connection test dialog and the empty Table list. I've managed to configure successfully the System DSN for my database and I can access to the content of the database from other software.įrom LibreOffice I manage to get the connection working but the existing tables in the database do not show up on the Tables list. On my Mac OS X 10.7 with LibreOffice 3.5.0rc3 (I've installed the final 3.5.0 but the About dialog is still showing 3.5.0rc3). I'm using the 5.1.10 32-bit MySQL ODBC connector for Mac OS X 10.6 from
0 kommentar(er)
