[Date Prev][Date Next]
reusing transactions in LMDB
- To: firstname.lastname@example.org
- Subject: reusing transactions in LMDB
- From: Tim Uckun <email@example.com>
- Date: Mon, 21 Nov 2016 16:22:51 +1300
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=KIiejJ6xUOu3yMhWo2zDygVHqMHfg5h2onQLQ9Q13/k=; b=WhY2lVJAilYYaO1AGjDZcAu26Aju1zMlUXHC/B//RdoAX6jCDlA1iHWoj5l5s37+c4 GbR3/N679C8JyVJ8rP/WX4/YPBVYSqScI1WwlDQzzAkrQlv8wpcBTV139K/NDemA9zsa BGXqQxpXr1hd+23W5DS/jlZYNxsgXkouGarEHHhho/1U+B/knXWIfo2mPIT+skxmFSQL Au1DUj3b86bKwoL8C6DclJa/ewOL39rfU2N3fAt7HnqqLHE1eKZlwjZRDg8XXaJtyUII Z7hlybH1bhWryr5yT6oSkSCnIxfDS86xIXUjAVblrtggiJjOubWggN779rsPIpSzVwz9 9Wpg==
Another question regarding my wrapper for lmdb.
The comments say it's possible to reuse read only transactions but says nothing about reusing the read write transactions. Does this mean every write operation needs a fresh transaction? Is there any downsides to not implementing the reuse functions for the wrapper? I figure the use case is quite limited and frankly I would have to manage all the transaction pointers to make sure they were being used property.
Also I noticed that every call to mdb_txn_id returns 1 even for different transactions. Is this normal?