new lines not recognised in ripgrep
by - Thursday, January 1, 1970 at 12:00 AM
Hi everyone

Have had this issue for a while while searching certain databases using ripgrep.

For most databases its not an issue. You put in your search and ripgrep delivers the results per the line they appear in the file.


For a few databases (primarily Zynga and Wishbone) however it seems to not be able to detect a new entry/new line and lists a whole bunch of results under the one line.


Anyone know what I'd need to do to the database files (mainly .sql files) to get them to be read line by line in ripgrep ?
Reply
it does detect a new line, but in the sql the insert statements entries are all on the same line. so u need to either manually replace ),( with new line or import to mysql and export as csv
Reply
(October 15, 2022, 06:07 PM)opulent_accomplice Wrote: it does detect a new line, but in the sql the insert statements entries are all on the same line. so u need to either manually replace ),( with new line or import to mysql and export as csv


Thanks for this.

Have had trouble opening some of these files in mysql given the size. Will try again
Reply
Break the file up into multiple smaller chunks, and go through all those separately, in addition to the ),( to
replacement, if you run into ram issues.
Reply
(October 16, 2022, 05:04 AM)thelorax42 Wrote: Break the file up into multiple smaller chunks, and go through all those separately, in addition to the ),( to
replacement, if you run into ram issues.


Good suggestion, thanks
Reply


 Users viewing this thread: new lines not recognised in ripgrep: No users currently viewing.