[Rpm-maint] join wiki edit group; intro; cross development
skvidal at linux.duke.edu
Tue Jan 2 05:43:55 UTC 2007
On Thu, 2006-12-28 at 10:34 -0600, Mark Hatle wrote:
> I just wanted to add a clarification to my Berkley DB statement below (I
> have already changed the wiki page to match.)
> * A Berkley DB database HATES being created on one arch and used on
> another. The contents of the database are intact and read-able
> cross-endian. The problem is specific to locking. Different
> architectures do locking in different ways which may cause problems.
> (Clarified from original email.) It may be possible to build Berkley DB
> on different architectures with the same locking formats, however there
> may be endian specific items in the locking. (Also different
> architectures may not support the same type of locking. Read the BDB
> documentation when configuring the locking mechanisms.)
> * Note: sqlite was added to attempt to work around this issue. At a
> tradeoff of slower performance, and no concurrent transactions. Sqlite
> automatically addresses the locking issues in my experience.
If the database were restructured a bit would the sqlite implementation
gain much in speed? Especially if the data were broken out a bit more
and some indexes implemented?
More information about the Rpm-maint