https://github.com/fluffynuts/mysql-runner

A brute-force mysql file runner, eg for (mostly) restoring wonky backups
https://github.com/fluffynuts/mysql-runner

Last synced: 19 days ago
JSON representation

A brute-force mysql file runner, eg for (mostly) restoring wonky backups

• Host: GitHub
• URL: https://github.com/fluffynuts/mysql-runner
• Owner: fluffynuts
• License: bsd-3-clause
• Created: 2019-06-26T14:41:26.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2024-06-13T10:09:18.000Z (8 months ago)
• Last Synced: 2024-12-30T15:11:38.223Z (27 days ago)
• Language: C#
• Size: 2.22 MB
• Stars: 1
• Watchers: 3
• Forks: 3
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# mysql-runner

A brute-force mysql file runner, eg for (mostly) restoring (potentially) wonky backups or

resuming backups from existing sources without IGNOREs

## usage

Run with `--help` to get help any time and forget about this doc (:

```

MySql Runner

Usage: mysql-runner [options] script.sql ... {script2.sql}

  where options are of:

  -d {database}    set database (no default)

  -h {host}        set database host (defaults to localhost)

  -p {password}    set password to log in with (defaults empty)

  --prompt         will prompt for password

  -P {port}        set port (defaults to 3306}

  -s               stop on error (defaults to carry on)

  -q               quiet operations

  -u {user}        set user to log in with (defaults to root)

```

## why?

I needed to be able to restore scripts made by `mysqldump` and had to overcome:

- `mysql` would crash on long lines

- I wanted to be able to 'resume' so needed to be able to ignore errors

- I tried HeidiSQL and it predicted 22 hours to run in scripts that took this tool about 40 minutes

- I wanted something that would work cross-platform

- I've written something like this in the past before and lost it

- I wrote almost exactly this the day I created this repo and did `git reset --hard` and lost it :/

  - but then I made a new one (:

## situation [X] breaks!

Let me know about it -- raise an issue. The primary aim was to get a dump file running in without

interruption. So I _know_ that there are some naive assumptions, in particular that `/* ... */` is a

"multi-line comment which never actually spans multiple lines, but leaves a no-op query behind", eg:

```

/* some mysqldump options stuff goes here */;

```

so if you have legitimate multi-line comments or something useful after the comment, this tool won't

(currently) behave as expected. But it could, if you give me an example (: