In php I can use:-

mysql_connect("localhost", $user,$password);
mysql_select_db($database);

but using C API I have to use this:-


mysql_real_connect(&mysql,"127.0.0.1",USERNAME,PAS SWORD,DATABASE,0,"",0)

"localhost" or a null "" for the host, simply do not work..

anyone care to comment?

they are different databases, in each case, but the same user/password.

The Natural Philosopher <tnp (AT) invalid (DOT) invalid> writes:

The Mysql client library takes a different view of "localhost" than the
rest of the world does. Instead of resolving it like it would any other
host name, it takes it as a request to connect to the local domain
socket.

I suspect that PHP may be resolving the host name itself, and passing
the IP address to the C function.

sherm--

The Natural Philosopher <tnp (AT) invalid (DOT) invalid> wrote:
To mysql, localhost is not 127.0.0.1, it is a connection to a Unix socket
file on a local server.

http://dev.mysql.com/doc/refman/5.0/en/connecting.html

--
Jim Pennino

Remove .spam.sux to reply.

Sherm Pendley wrote:
an IP socket only?

How would I tell?

> sherm--

The Natural Philosopher <tnp (AT) invalid (DOT) invalid> writes:

You can tell because "127.0.0.1" works, and "localhost" does not. The
former uses an IP socket; the latter, a domain socket. PHP is apparently
obscuring the difference by resolving the host name itself, rather than
passing it as given to the C function.

sherm--

On 5/27/2011 11:59 AM, The Natural Philosopher wrote:
Your MySQL configuration is probably screwed up. PHP obviously knows
where to look for the Unix socket, but C doesn't. The most obvious
answer would be that the MySQL configuration has the wrong information
for the socket but the php.ini file overrides it with the correct
information.

Another possibility would be a security problem connecting to the MySQL
socket from your C application, which may be running under a different
user id.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex (AT) attglobal (DOT) net
==================

You have a configuration problem of some sort. Connecting to the Unix
socket from the C library should work.

The socket is normally named /tmp/mysql.sock -- any chance an overzealous
disk cleanup script deleted it?

R's,
John

John Levine wrote:

It could also be under /var/run or even /var/lib (either is betetr than /tmp
for the reasons given).

--
Tim Watts

Tim Watts wrote:

from /etc/mysql/my.cnf


[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently
parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0

[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
language = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
#