Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the KiokuDB CPAN distribution.

Report information
The Basics
Id: 58166
Status: open
Priority: 0/
Queue: KiokuDB
People
Owner: Nobody in particular
Requestors: hanenkamp [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Sat Jun 05 12:25:16 2010 hanenkamp [...] cpan.org - Ticket created
Subject: Expose txn_begin/commit/rollback
While txn_do() is definitely a best practice, it is sometimes easier to use txn_begin/commit/rollback. These are provided by back-ends implementing the TXN role, but is not provided by KiokuDB or KiokuDB::Role::API to us, the little people. Cheers, Sterling
  Sat Jun 05 12:35:53 2010 NUFFIN [...] cpan.org - Correspondence added
Subject: Re: [rt.cpan.org #58166] Expose txn_begin/commit/rollback
Date: Sat, 5 Jun 2010 19:35:24 +0300
To: bug-KiokuDB [...] rt.cpan.org
From: Yuval Kogman <nuffin [...] cpan.org>
FWIW, I see $dir->backend as perfectly fair game for the end user, since it supports various extensions to the API. That said, I'll add these to the next release anyway.
  Sat Jun 05 12:35:56 2010 The RT System itself - Status changed from 'new' to 'open'
  Sat Jun 05 12:47:03 2010 NUFFIN [...] cpan.org - Status changed from 'open' to 'resolved'
  Mon Jun 14 11:07:55 2010 NUFFIN [...] cpan.org - Correspondence added
Bah, now I remembered why I didn't expose these. txn_begin can return a txn handle which txn_commit/rollback can expect to get back as an argument. I think I'm going to roll back this change because the BDB backend relies on this and it's going to be hard to expect the users to comply actually comply with this. If you'd like to implement a stack in KiokuDB.pm to manage this, then be my guest, but please make it pretty anal about providing errors)
  Mon Jun 14 11:07:56 2010 The RT System itself - Status changed from 'resolved' to 'open'