> Would you please try the same with sqlite3 and/or > libdbd-sqlite3-perl ? As sqlite v2 does not maintained > anymore, everyone should use sqlite v3. So I can do nothing to > get this fixed in sqlite v2, but if you confirm the same with > sqlite v3, then I'll bug upstream.
Ugh, filling /var on purpose is always unpleasant thing to do. I finally did it and it seems that in sqlite3 this problem is not present. PS If sqlite2 is not maintained, maybe it should be dropped? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
