On Wed, May 09, 2001 at 10:51:44AM -0400, Bill Moran wrote:
> Peter Pentchev wrote:
> > So, MySQL 3.22.x does not have the capability to produce dumpfiles,
> > only outfiles.
> >
> > Ah. I just read the whole of your message. You are using a 3.22.32 server -
> > so, sorry, but you're out of luck :(
>
> AHHHH!!!! Curses, I was hoping to avoid an upgrade (since we've had
> nothing but trouble with other clients accessing this server and I don't
> want to shake things up with an upgrade!)
>
> But, really, that answers my question - the SERVER must be >3.23.6.
> Apparently the client makes little difference. I'll also have to NFS
> mount the file sever to the SQL server to get the file where I want it.
> It's a pain, but at least I have an answer.
Well, SELECT INTO [OUTFILE | DUMPFILE] is a server-side operation, as (again)
clearly outlined in the docs :)
* The `SELECT ... INTO OUTFILE 'file_name'' form of `SELECT' writes
the selected rows to a file. The file is created on the server
host and cannot already exist...
So.. yes, you'll have to upgrade the server to use SELECT INTO DUMPFILE.
G'luck,
Peter
--
I had to translate this sentence into English because I could not read the original
Sanskrit.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
