Closed GoogleCodeExporter closed 9 years ago
It seems sqlite database has expiration field marked as NOT NULL, when it
should be nullable. I guess I have to release an update for the share plugin
that corrects this.
If you have sqlite manager etc where you can make this change, you can do it
right away.
Original comment by samuli.j...@gmail.com
on 12 Jul 2012 at 6:48
You could try running this sqlite script (although I haven't yet tested it):
CREATE TEMPORARY TABLE share_backup(id,item_id,name,user_id,expiration,created,
active);
INSERT INTO share_backup SELECT id,item_id,name,user_id,expiration,created,
active FROM share;
DROP TABLE share;
CREATE TABLE share (
id char(32) PRIMARY KEY,
item_id char(255) NOT NULL,
name varchar(255) NOT NULL,
user_id INTEGER NOT NULL,
expiration bigint(11) NULL,
created bigint(11) NOT NULL,
active TINYINT(1) NOT NULL
);
INSERT INTO share SELECT id,item_id,name,user_id,expiration,created, active
FROM share_backup;
DROP TABLE share_backup;
Original comment by samuli.j...@gmail.com
on 12 Jul 2012 at 7:34
Fixed in 1.8.9
Original comment by samuli.j...@gmail.com
on 22 Jul 2012 at 12:18
Original issue reported on code.google.com by
hanta...@gmail.com
on 12 Jul 2012 at 5:33Attachments: