Remove album size caching from to do list.
With the recent improvements in album size determination this is not necessary.
This commit is contained in:
		
							parent
							
								
									a12d8cada1
								
							
						
					
					
						commit
						79465b803e
					
				
					 1 changed files with 0 additions and 1 deletions
				
			
		|  | @ -80,7 +80,6 @@ Here is a brief overview of the project to help you learn your way around: | ||||||
| - Some way for the database to re-identify a file that was moved / renamed (lost & found). Maybe file hash of the first few mb is good enough. | - Some way for the database to re-identify a file that was moved / renamed (lost & found). Maybe file hash of the first few mb is good enough. | ||||||
| - Debate whether the `UserMixin.login` method should accept usernames or I should standardize the usage of IDs only internally. | - Debate whether the `UserMixin.login` method should accept usernames or I should standardize the usage of IDs only internally. | ||||||
| - Ability to access user photos by user's ID, not just username. | - Ability to access user photos by user's ID, not just username. | ||||||
| - Should album size be cached on disk? |  | ||||||
| - Replace columns like area, ratio, bitrate by using expression indices or views (`width * height` etc). | - Replace columns like area, ratio, bitrate by using expression indices or views (`width * height` etc). | ||||||
| - Add a `Photo.merge` to combine duplicate entries. | - Add a `Photo.merge` to combine duplicate entries. | ||||||
| - Generate thumbnails for vector files without falling victim to bombs. | - Generate thumbnails for vector files without falling victim to bombs. | ||||||
|  |  | ||||||
		Loading…
	
		Reference in a new issue