Felix Kauselmann 4b3042def4 
	
	
	Fix object leaks in database code ... 
			Qt's database and query model requires that both the queries and the database
objects are out of scope before a database connection can safely be removed.
Solution: Properly encapsulate databases and queries in "{ }" and use a string
to cache the connection name for out-of-scope removal. 
		
	 
		2020-08-25 17:34:46 +02:00 
	 
	
	
		 
	
	
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-05-30 19:46:37 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-09-25 17:38:59 +02:00 
		 
	
		
			
			
			
			
			
			2019-09-25 17:38:59 +02:00 
		 
	
		
			
			
			
			
			
			2020-08-25 17:34:46 +02:00 
		 
	
		
			
			
			
			
			
			2019-09-25 17:38:59 +02:00 
		 
	
		
			
			
			
			
			
			2018-08-07 11:09:02 +02:00 
		 
	
		
			
			
			
			
			
			2019-05-30 19:46:37 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-05-30 19:46:37 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-05-30 19:46:37 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-05-30 19:46:37 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-05-30 19:46:37 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2020-07-24 21:17:49 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2020-07-24 21:17:49 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2020-07-24 21:17:49 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00 
		 
	
		
			
			
			
			
			
			2019-06-01 16:04:48 +02:00