Sqlite cache needs updating reading in metadata
This moves the logic to the storage handler, which should hopefully give us the best of both worlds. Phenaproxima noticed that other external metadata could have the same issues as the thumbnail downloads.
Slow API's could cause even fetching the name metadata to be slow.
= NULL' failed Traceback (most recent call last): File "/usr/bin/yum", line 29, in ?
yummain.main(sys.argv[1:])File "/usr/share/yum-cli/yummain.py", line 97, in mainresult, resultmsgs = do()File "/usr/share/yum-cli/cli.py", line 534, in do Commandsypl = self.return Pkg Lists()File "/usr/share/yum-cli/cli.py", line 1176, in return Pkg Listsypl = Package Lists(pkgnarrow=pkgnarrow)File "__init__.py", line 904, in do Package Lists File "/usr/share/yum-cli/cli.py", line 75, in do Repo Sack Setup(thisrepo=thisrepo)File "__init__.py", line 260, in do Sack Setup File "repos.py", line 277, in populate Sack File "/usr/lib64/python2.3/site-packages/sqlitecachec.py", line 40,in get Primaryself.repoid))Type Error: Can not create index on requires table: near "NOT": syntax error This is the output of rpm -qa | grep sqlite[[email protected] ~]# rpm -qa | grep sqlitepython-sqlite-1.1.7-1.2.1sqlite-3.3.6-2sqlite-devel-3.3.6-2any suggestions ?
For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.
Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch.
This will almost certainly break tests, but it illustrates the solution I had in mind for this knotty problem.
It's nice to have the slickness of thumbnail updates being part of the save operation, but it's extremely dicey and bad to have that logic be part of the Media entity class.
Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch.The example below demonstrates how to use either method. It is to be placed in the assets folder of the project for the internal method or copied into the "Execute SQL' of SQLite Manager to create the database for the external method. SQLite Open Helper; /** * @author Danny Remington - Macro Solve * * Helper class for sqlite database.