Is there enough of a difference in the way this works that the two versions would handle mysqlimport different? My testing server is running v4.0.12 and I can run a specific mysqlimport string all day long and it runs without error ... however, when I run the same command on the v.3.23 it wont run at all, says: "ERROR: The used command is not allowed with this MySQL version, when using the table: tableX"
I've tried rewriting the command and restructuring it with no success.
The text file I am trying to import is a CSV located on a mapped network drive (G:\) ... the v3.23 server is where I am trying to run the command.
If I have to upgrade to v4 then I will ... but would rather not have to come in over July 4th weekend to make that happen.
The exact command string I am working with is here:
C:\mysql\bin>mysqlimport -u upload pulsa "g:\iss\jdeoutput\pga_rma_jdeoutput" --fields-terminated-by="," --fields-optionally-enclosed-by=""" --local --verbose --replace
BTW, this an under Win2k SP3, the network security isnt an issue since I Am running this as the Domain Admin account ... *shrug*
Any help would be greatly appreciated.
Matt Laski
Sysadmin, Pulsafeeder Inc.
I've tried rewriting the command and restructuring it with no success.
The text file I am trying to import is a CSV located on a mapped network drive (G:\) ... the v3.23 server is where I am trying to run the command.
If I have to upgrade to v4 then I will ... but would rather not have to come in over July 4th weekend to make that happen.
The exact command string I am working with is here:
C:\mysql\bin>mysqlimport -u upload pulsa "g:\iss\jdeoutput\pga_rma_jdeoutput" --fields-terminated-by="," --fields-optionally-enclosed-by=""" --local --verbose --replace
BTW, this an under Win2k SP3, the network security isnt an issue since I Am running this as the Domain Admin account ... *shrug*
Any help would be greatly appreciated.
Matt Laski
Sysadmin, Pulsafeeder Inc.