Open CharlesBelov opened 5 years ago
Reopening with corrected description.
If I attempt to run mysqldumpsplitter.sh in MINGW64 on Windows 10 on a file that has a space in its file path, the attempt fails.
Given file '/m/backups/190902 backups/2019-09-03T18-07-11_UTC_database.sql'
$ mysqldumpsplitter.sh --extract ALLTABLES --decompression none --source '/m/backups/190902 backups/2019-09-03T18-07-11_UTC_database.sql'
Expected result: mysqldumpsplitter.sh processes the file.
Actual result:
mysqldumpsplitter.sh: line 342: [: /m/backups/190902: binary operator expected mysqldumpsplitter.sh: line 95: [: /m/backups/190902: binary operator expected mysqldumpsplitter.sh: line 99: [: /m/backups/190902: binary operator expected Setting compression gzip (default). Setting no decompression. File /m/backups/190902 backups/2019-09-03T18-07-11_UTC_database.sql is a regular dump. Setting output directory: out. Processing: Extract ALLTABLES from /m/backups/190902 backups/2019-09-03T18-07-11_UTC_database.sql with compression option as gzip and output location as out cat: /m/backups/190902: No such file or directory cat: backups/2019-09-03T18-07-11_UTC_database.sql: No such file or directory Total tables extracted.
Withdrawing issue for better definition. Okay to close.