On 21 Mar 2002, at 12:11, David M. Peak wrote: > Is there a way to tell MySQL to put a blank space instead of \N in the > tab-delimited files when it does a dump? I'm working on a MySQL to SQL > Server migration and having problems with the output files.
If you don't care about the distinction between nulls and blanks, then just change the table. If you do care, how do you plan to distinguish between them on import? Maybe you're just talking about numeric fields. I guess you could do the dump as a series of SELECT ... INTO OUTFILE statements and transform the NULLs into whatever you wanted, rather than using mysqldump. > I'm doing this > all in batch fellas so I'm not finding a good search and replace utility. > (perl, c++, and other langs are not an option..) Why aren't they an option? Perl is an extremely easy solution to your problem (you can use a one-liner in your batch file), and if you don't tell us why it won't work we can't know what other solutions you've arbitrarily excluded. -- Keith C. Ivey <[EMAIL PROTECTED]> Washington, DC --------------------------------------------------------------------- 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
