Message 284585 - Python tracker

➜

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	Big Stone, berker.peksag, callidomus, fschulze, ghaering, jaraco, malin, ned.deily, palaviv, r.david.murray, serhiy.storchaka, socketpair, xiang.zhang
Date	2017-01-03.18:02:01
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
Yes. If a transaction is open you will need to explicitly commit before doing vacuum. I am not sure if that was intentional or not. From quick look in the sqlite source code there are few things that cannot happen from a transaction: 1. VACUUM 2. ATTACH 3. DETACH 4. BEGIN 5. Few PRAGMAs (temp_store, synchronous) All of the above worked with implicit commit before commit 284676cf2ac8 but now has to call commit explicitly.

Yes. If a transaction is open you will need to explicitly commit before doing vacuum.
I am not sure if that was intentional or not. From quick look in the sqlite source code there are few things that cannot happen from a transaction:
1. VACUUM
2. ATTACH
3. DETACH
4. BEGIN
5. Few PRAGMAs (temp_store, synchronous)

All of the above worked with implicit commit before commit 284676cf2ac8 but now has to call commit explicitly.

History
Date	User	Action	Args
2017-01-03 18:02:02	palaviv	set	recipients: + palaviv, ghaering, jaraco, ned.deily, r.david.murray, socketpair, berker.peksag, serhiy.storchaka, malin, xiang.zhang, Big Stone, fschulze, callidomus
2017-01-03 18:02:02	palaviv	set	messageid: <[email protected]>
2017-01-03 18:02:02	palaviv	link	issue28518 messages
2017-01-03 18:02:01	palaviv	create