| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| fix_pod_spelling | fix POD spelling errors | Angel Abad <angelabad@gmail.com> | yes | vendor | 2016-10-21 | |
| sqlite-vacuum.patch | Fix cleanup in tests. Since SQLite 3.15, VACUUM either needs no arguments, or the name of an attached database. . From https://sqlite.org/lang_vacuum.html : Compatibility Warning: The ability to vacuum attached databases was added in version 3.15.0 (2016-10-14). Prior to that, a schema-name added to the VACUUM statement would be silently ignored and the "main" schema would be vacuumed. . That means that 'VACUUM ANALYZE' never did what it was probably supposed to do. . Maybe 'VACUUM; ANALYZE' works as well. -- And besides this change in the testsuite, the documentation for cleanup() in the POD would need to be updated as well. . |
gregor herrmann <gregoa@debian.org> | yes | debian upstream | vendor | 2016-10-21 |
| sqlite-case-insensitive.patch | Fix test failure with SQLite 3.37.0 # Failed test '->table_info ok' # at t/21_normalize.t line 62. # Structures begin differing at: # $got->[0]{type} = 'INTEGER' # $expected->[0]{type} = 'integer' . Use Test::Deep to check against case-insensitve regexp. |
gregor herrmann <gregoa@debian.org> | yes | upstream | vendor | 2022-01-17 |