This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author palaviv
Recipients Ingo Ruhnke, berker.peksag, ghaering, palaviv
Date 2017-04-15.18:18:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1492280327.44.0.755888047822.issue29021@psf.upfronthosting.co.za>
In-reply-to
Content
In my patch I use sqlite3_create_function_v2 which was added in sqlite 3.7.3 (2010-10-08). There were a few problems after adding sqlite3_stmt_readonly in 284676cf2ac8 as can be seen in issue #29355. sqlite3_stmt_readonly was added in 3.7.4 (2010-12-07) so I guess using sqlite3_create_function_v2 will cause the same problems.

Do you think I should find another way to fix this issue? I can follow all the user functions and free on my own but that will make the code more complex. On the other hand I can add this fix in ifdef and the behavior will be different when using sqlite in versions smaller then 3.7.3.
History
Date User Action Args
2017-04-15 18:18:47palavivsetrecipients: + palaviv, ghaering, berker.peksag, Ingo Ruhnke
2017-04-15 18:18:47palavivsetmessageid: <1492280327.44.0.755888047822.issue29021@psf.upfronthosting.co.za>
2017-04-15 18:18:47palavivlinkissue29021 messages
2017-04-15 18:18:47palavivcreate