Separate version_pragma from other pragmas!
This was a dumb bug. Because the version was included in the pragmas that get set on every load, the database was receiving the new user_version simply by setting skip_version_check=False and letting the regular pragmas load, so all future checks passed without having to run the db upgrader.
This commit is contained in:
		
							parent
							
								
									222d63857e
								
							
						
					
					
						commit
						93eb693bee
					
				
					 1 changed files with 5 additions and 1 deletions
				
			
		|  | @ -43,15 +43,19 @@ ffmpeg = _load_ffmpeg() | |||
| # Database ######################################################################################### | ||||
| 
 | ||||
| DATABASE_VERSION = 14 | ||||
| DB_VERSION_PRAGMA = f''' | ||||
| PRAGMA user_version = {DATABASE_VERSION}; | ||||
| ''' | ||||
| 
 | ||||
| DB_PRAGMAS = f''' | ||||
| PRAGMA cache_size = 10000; | ||||
| PRAGMA count_changes = OFF; | ||||
| PRAGMA foreign_keys = ON; | ||||
| PRAGMA user_version = {DATABASE_VERSION}; | ||||
| ''' | ||||
| 
 | ||||
| DB_INIT = f''' | ||||
| {DB_PRAGMAS} | ||||
| {DB_VERSION_PRAGMA} | ||||
| ---------------------------------------------------------------------------------------------------- | ||||
| CREATE TABLE IF NOT EXISTS users( | ||||
|     id TEXT PRIMARY KEY NOT NULL, | ||||
|  |  | |||
		Loading…
	
		Reference in a new issue