![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I want to export SQL data using BCP.EXE and for normal operation everything's fine. The default record delimiter of "\n" gets mapped to 0x0D, 0x0A and this works for the PC/Windows. But when I want to export data for a UNIX system, I don't know how to tell BCP to really just spit out a single line feed (0x0A) and not the CR/LF pair. I can successfully export for Macintosh by using "-r \r" and only a 0x0D is emitted. Yes, I can play tricks like emitting just the CR and then running the output through a tr-like utility to change the 0x0D characters into 0x0A, but it sure would be nice to bcp out the data with the right record terminators to begin with!! Is there a way to tell bcp.exe *not* to cook the line endings and treat \n as just a linefeed?!? |
#3
| |||
| |||
|
|
I want to export SQL data using BCP.EXE and for normal operation everything's fine. The default record delimiter of "\n" gets mapped to 0x0D, 0x0A and this works for the PC/Windows. But when I want to export data for a UNIX system, I don't know how to tell BCP to really just spit out a single line feed (0x0A) and not the CR/LF pair. I can successfully export for Macintosh by using "-r \r" and only a 0x0D is emitted. Yes, I can play tricks like emitting just the CR and then running the output through a tr-like utility to change the 0x0D characters into 0x0A, but it sure would be nice to bcp out the data with the right record terminators to begin with!! Is there a way to tell bcp.exe *not* to cook the line endings and treat \n as just a linefeed?!? |
#4
| |||
| |||
|
|
I want to export SQL data using BCP.EXE and for normal operation everything's fine. The default record delimiter of "\n" gets mapped to 0x0D, 0x0A and this works for the PC/Windows. But when I want to export data for a UNIX system, I don't know how to tell BCP to really just spit out a single line feed (0x0A) and not the CR/LF pair. I can successfully export for Macintosh by using "-r \r" and only a 0x0D is emitted. Yes, I can play tricks like emitting just the CR and then running the output through a tr-like utility to change the 0x0D characters into 0x0A, but it sure would be nice to bcp out the data with the right record terminators to begin with!! Is there a way to tell bcp.exe *not* to cook the line endings and treat \n as just a linefeed?!? |
#5
| |||
| |||
|
|
I want to export SQL data using BCP.EXE and for normal operation everything's fine. The default record delimiter of "\n" gets mapped to 0x0D, 0x0A and this works for the PC/Windows. But when I want to export data for a UNIX system, I don't know how to tell BCP to really just spit out a single line feed (0x0A) and not the CR/LF pair. I can successfully export for Macintosh by using "-r \r" and only a 0x0D is emitted. Yes, I can play tricks like emitting just the CR and then running the output through a tr-like utility to change the 0x0D characters into 0x0A, but it sure would be nice to bcp out the data with the right record terminators to begin with!! Is there a way to tell bcp.exe *not* to cook the line endings and treat \n as just a linefeed?!? |
#6
| |||
| |||
|
|
I want to export SQL data using BCP.EXE and for normal operation everything's fine. The default record delimiter of "\n" gets mapped to 0x0D, 0x0A and this works for the PC/Windows. But when I want to export data for a UNIX system, I don't know how to tell BCP to really just spit out a single line feed (0x0A) and not the CR/LF pair. I can successfully export for Macintosh by using "-r \r" and only a 0x0D is emitted. Yes, I can play tricks like emitting just the CR and then running the output through a tr-like utility to change the 0x0D characters into 0x0A, but it sure would be nice to bcp out the data with the right record terminators to begin with!! Is there a way to tell bcp.exe *not* to cook the line endings and treat \n as just a linefeed?!? |
#7
| |||
| |||
|
|
I want to export SQL data using BCP.EXE and for normal operation everything's fine. The default record delimiter of "\n" gets mapped to 0x0D, 0x0A and this works for the PC/Windows. But when I want to export data for a UNIX system, I don't know how to tell BCP to really just spit out a single line feed (0x0A) and not the CR/LF pair. I can successfully export for Macintosh by using "-r \r" and only a 0x0D is emitted. Yes, I can play tricks like emitting just the CR and then running the output through a tr-like utility to change the 0x0D characters into 0x0A, but it sure would be nice to bcp out the data with the right record terminators to begin with!! Is there a way to tell bcp.exe *not* to cook the line endings and treat \n as just a linefeed?!? |
#8
| |||
| |||
|
|
I want to export SQL data using BCP.EXE and for normal operation everything's fine. The default record delimiter of "\n" gets mapped to 0x0D, 0x0A and this works for the PC/Windows. But when I want to export data for a UNIX system, I don't know how to tell BCP to really just spit out a single line feed (0x0A) and not the CR/LF pair. I can successfully export for Macintosh by using "-r \r" and only a 0x0D is emitted. Yes, I can play tricks like emitting just the CR and then running the output through a tr-like utility to change the 0x0D characters into 0x0A, but it sure would be nice to bcp out the data with the right record terminators to begin with!! Is there a way to tell bcp.exe *not* to cook the line endings and treat \n as just a linefeed?!? |
#9
| |||
| |||
|
|
I want to export SQL data using BCP.EXE and for normal operation everything's fine. The default record delimiter of "\n" gets mapped to 0x0D, 0x0A and this works for the PC/Windows. But when I want to export data for a UNIX system, I don't know how to tell BCP to really just spit out a single line feed (0x0A) and not the CR/LF pair. I can successfully export for Macintosh by using "-r \r" and only a 0x0D is emitted. Yes, I can play tricks like emitting just the CR and then running the output through a tr-like utility to change the 0x0D characters into 0x0A, but it sure would be nice to bcp out the data with the right record terminators to begin with!! Is there a way to tell bcp.exe *not* to cook the line endings and treat \n as just a linefeed?!? |
#10
| |||
| |||
|
|
I want to export SQL data using BCP.EXE and for normal operation everything's fine. The default record delimiter of "\n" gets mapped to 0x0D, 0x0A and this works for the PC/Windows. But when I want to export data for a UNIX system, I don't know how to tell BCP to really just spit out a single line feed (0x0A) and not the CR/LF pair. I can successfully export for Macintosh by using "-r \r" and only a 0x0D is emitted. Yes, I can play tricks like emitting just the CR and then running the output through a tr-like utility to change the 0x0D characters into 0x0A, but it sure would be nice to bcp out the data with the right record terminators to begin with!! Is there a way to tell bcp.exe *not* to cook the line endings and treat \n as just a linefeed?!? |
![]() |
| Thread Tools | |
| Display Modes | |
| |