[pkg-bacula-devel] Bug#909460: Trouble with the sqlite3 upgrade path

Sven Hartge sven at svenhartge.de
Mon Sep 24 13:33:21 BST 2018

On 9/24/18 12:46 PM, Sven Hartge wrote:
> On 9/24/18 10:07 AM, Carsten Leonhardt wrote:
>> according to piuparts:
>>   applying upgrade sql for 7.4.4+dfsg-6 -> 9.0.0.
>>   Error: near line 84: near "MODIFY": syntax error
>>   Error: near line 85: near "MODIFY": syntax error
>>   Error: near line 86: near "MODIFY": syntax error
>> https://piuparts.debian.org/stable2sid/fail/bacula-director-sqlite3_9.2.1-1.log
>> The version in stretch-backports contains the 9.0.0 update too but
>> stretch2bpo works ok.
> According to the sqlite3 documentation, "ALTER TABLE table-name MODIFY"
> is indeed invalid. But we had this patch for some releases.
> https://www.sqlite.org/lang_altertable.html
> Maybe this was changed in a recent sqlite release?

Doesn't look like it, but maybe sqlite3 3.16 was more forgiving?

Looking at the code, it seems we have to create a temp table with the
new schema and then select everything from the old table into it, then
removing the old table and finally renaming the temp table.

Just like it was done with basefiles_temp.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20180924/8d145a85/attachment.sig>

More information about the pkg-bacula-devel mailing list