Timeline for Skipping lines in a large file, then pipe to external command in Nushell
Current License: CC BY-SA 4.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 17, 2022 at 16:30 | comment | added | NotTheDr01ds | @Prem Ah, got it. I get the feeling the OP was just trying to replicate the Bash version in Nushell. | |
Sep 17, 2022 at 8:10 | comment | added | Prem | What I intended to say was :: "When OP converted sql.gz to sql, OP could very well have removed the 46 lines making sql-46 , then mysql can Directly use that new file sql-46 without getting into nushell Issues" :: Your Solution in nushell works too, but this is one alternative without nushell ! | |
Sep 16, 2022 at 22:13 | vote | accept | Hut8 | ||
Sep 16, 2022 at 21:39 | comment | added | NotTheDr01ds |
@Prem (A) I edited the question to clarify the name-mismatch, since it's explained in the OP's Github issue on the same topic. (B) would run into the same issue (would try to process the entire file in memory before writing to filename-46.sql ) as long as to text is being used.
|
|
Sep 16, 2022 at 21:34 | history | edited | NotTheDr01ds | CC BY-SA 4.0 |
Brought in some information from the OP's Github issue on the same topic on in the Nushell repo (https://github.com/nushell/nushell/issues/6570)
|
Sep 16, 2022 at 21:27 | answer | added | NotTheDr01ds | timeline score: 2 | |
Sep 16, 2022 at 14:40 | comment | added | Prem |
(A) In zcat filename.sql.gz & in open --raw filename.sql we have file name mismatch. Is that intentional ? (B) Can you make filename-46.sql earlier (one time) to use that Directly on mysql ?
|
|
Sep 16, 2022 at 14:01 | history | asked | Hut8 | CC BY-SA 4.0 |