This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 219012

Summary: netbeans doesn't recognize mysql
Product: db Reporter: medeag
Component: MySQLAssignee: Libor Fischmeistr <lfischmeistr>
Status: NEW ---    
Severity: normal CC: jrechtacek, musilt2
Priority: P4    
Version: 7.3   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:

Description medeag 2012-09-25 17:56:40 UTC
Product Version: NetBeans IDE 7.3 Beta (Build 201209232010)
Java: 1.7.0_10-ea; Java HotSpot(TM) 64-Bit Server VM 23.6-b02
System: Mac OS X version 10.7.4 running on x86_64; US-ASCII; ka_GE (nb)

using with clean user dirs, no settings are imported from previous version.

from sanity test:

Open Windows | Services

EXPECTED RESULT:
Under Databases, MySQL is present.

reality:
netbeans didn't recognize mysql, i was forced to register it manually, in spite the fact that i'm using default 3306 port.
Comment 1 Jaroslav Havlin 2012-09-26 14:28:37 UTC
It seems that NetBeans failed to detect MySQL installation directory. Its needed to to start and stop the server, for example.

Currently, NetBeans support only MAMP installations with "/bin/startMysql.sh" and "/bin/stopMysql.sh" scripts. Are these two files available on your system?
If not, what is your MySQL installation directory?
Thank you.
Comment 2 medeag 2012-09-26 19:23:55 UTC
I don't use MAMP, so that might be the reason.  

my installation path is: /usr/local/mysql-5.5.8-osx10.6-x86_64

I'm not 100% sure but i think  i never bumped into this issue previous versions...
Comment 3 Jaroslav Havlin 2012-11-13 12:16:21 UTC
*** Bug 222035 has been marked as a duplicate of this bug. ***
Comment 4 Jaroslav Havlin 2012-11-13 12:55:17 UTC
The bug is not specific to Mac.
Detection of MySQL failed also on Win XP where it was installed in
C:\Program Files\MySQL\MySQL Server 5.5\bin (see bug 222035).
Comment 5 matthias42 2016-06-24 19:44:02 UTC
*** Bug 175278 has been marked as a duplicate of this bug. ***