Issue 35654

Summary: Database driver for Berkeley DB files
Product: Base Reporter: ronjohn <ron.l.johnson>
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: OOo 1.0.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---

Description ronjohn 2004-10-16 20:07:02 UTC

(I queried IssueZilla about this, but couldn't find anything.  Obviously, I used
the wrong keywords.  Sorry if this is a duplicate.)

This type of ISAM file is very popular on Unixish systems.

A specific would be the addressbook.db used by Evolution, the Unix groupware
suite.  This way, one could do mailmerges from his/her address book.
Comment 1 Frank Schönheit 2004-10-18 08:54:34 UTC
Berkely DB itself is not really a relational database, for instance, it does not
have a query engine. Nevertheless, it would be possible to have an driver
accessing BDB backend files.

Though, personally I think it wouldn't make too much sense. For example, for an
Evolution Address Book, I would not like us to access to BDB files directly.
Finally, they are an implementation detail of Evolution, which can change
without any notice. Instead, applications which use BDB to store <whatever>
data, should provide an official API to access this <whatever> data.
(In fact, this is what Evolution 2.0 is doing for its address books. Even
better, the Ximian guys already implemented an SDBC driver accessing this API. I
still hope they'll contribute this back to OOo.)

But, anyway, I suppose this is a valid RFE which might have some useful
applications. I confirm this as RFE, and assign it to the user experience team
for evaluation/consideration.
Comment 2 bettina.haberer 2010-05-21 15:11:20 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".