SQLITE_ERROR - the database migrations not working

[Saibamen]

Describe the bug

I wanted to test #86 on my localhost, but the migration code are broken, and latest migration was not applied.

[Error: update `monitor` set `name` = 'Monitor with invalid URL', `active` = 1, `user_id` = 1, `interval` = 60, `url` = 'https://wwww', `type` = 'http', `weight` = 2000, `hostname` = NULL, `port` = NULL, `created_date` = 1626651023, `keyword` = NULL, `maxretries` = '1' where `id` = 5 - SQLITE_ERROR: no such column: maxretries] {
  errno: 1,
  code: 'SQLITE_ERROR'
}

Server logs:

Your database version: 0
Latest database version: 1
Database patch is needed
Backup the db
Patching ./db/patch1.sql
Patched ./db/patch1.sql
Database Patched Successfully

Latest database version should be 3 (https://github.com/louislam/uptime-kuma/blob/master/db/patch3.sql).

To Reproduce
Steps to reproduce the behavior:

1. Go back to commit before merging Implement retries (#56) #86, for example: 5bd3184
2. Delete database and setup Uptime Kuma
3. Add Monitor
4. Pull latest changes from master branch
5. Update Retries field for Monitor

Expected behavior
No SQLITE_ERROR

Desktop (please complete the following information):

• Uptime Kuma Version: 1.0.6 dev d556509
• Using Docker?: No
• OS: Win 10
• Browser: ---

[louislam]

Sorry about that, because I added patch3.sql to master branch before merge the pull request #91 (patch2.sql in here).
You could patch the database manually first if you need development.

[Saibamen]

Can we add some warning in Server about it?

For example, if *.sql files != Latest_database_version - display console.warn('Some patches could not be applied. If you are running official release - please create bug report')