 |
 |
I run into one somewhat puzzling behavior: if you attempt to connect using host="localhost", mysql will check if they can find any reasonably looking socket in default locations, and if they do, they will silently use that. Of course that can completely derail qserv, because that means all of a sudden we are talking to a default system-installed mysqld and not our dedicated mysqld. Various MySQL tools have "protocol=TCP" flag which can be used to enforce host/port and overwrite this behavior, but there is no similar flag in connect() in mysqldb or c mysql api. The trick is to never use "localhost", and use "127.0.0.1" instead. Jacek On 01/10/2014 12:45 PM, Wang, Daniel Liwei wrote: > Jacek, > > Do you want to post your experiences with undocumented/surprising > behavior in the mysql CAPI to our developer blog? That's what it was > for, no? > > -Daniel > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1