|
|
Posted by Norman Peelman on 11/08/06 23:11
"Jim Carlock" <anonymous@127.0.0.1> wrote in message
news:pPq4h.6788$Bl1.1437@tornado.tampabay.rr.com...
> Jim Carlock wrote:
> : Does anyone here know if there's a version of (corrected) MySQL
> : that doesn't use TCP/IP, and instead uses the native file system
> : to write data to files?
>
> "Jerry Stuckle" <jstucklex@attglobal.net> posted:
> : PHP works quite well with the native file system. MySQL uses TCP/IP
> : for remote connections and local connections on Windows; it uses
> : sockets on Windows.
>
> Oops, yeah, I meant to question MySQL's ability to write natively to
> the file system, rather than writing through TCP/IP. Thanks for catching
> that. I think I'll take a look at some MySQL source code.
>
> : maybe comp.databases.mysql?
>
> Seems like that one dropped out of their lists of newsgroups. Wonder
> if TimeWarner will allow me to post to it?
>
> Nope...
>
> (I wonder why they dropped it.)
>
> Thanks.
>
> --
> Jim Carlock
> Post replies to the group.
>
>
MySQL does write natively to the filesystem... it receives and transmits
that data over TCP/IP, named pipes, etc. when needed. It's all in how you
open the connection.
mysql_connect('localhost', $user, $pass) <- named pipe
mysql_connect('127.0.0.1', $user, $pass) <- TCP/IP loopback same machine
mysql_connect('xxx.xxx.xxx.xxx', $user, $pass) <- TCP/IP
Norm
Navigation:
[Reply to this message]
|