That would be nice. Personally I always use a database abstraction layer of some kind so it's easy to choose your backend. As I mentioned, mysql and postgres would be a far cleaner setup for us in particular, and I'd like to see that here.

Joseph Oreste Bruni wrote:
On Feb 14, 2009, at 3:59 PM, Alex Roper wrote:

on issues (need to run reconstruction every day), as I usually notice with bdb-based applications.

In defense of BDB, I have written a multi-process application (in C) that handles billions of transactions per year, and I have never encountered any database corruption. The application has been running non-stop for the past four years.

It wasn't always so, however. It took me some time to make sure I was doing everything correctly.

So perhaps what you're asking for is not a database that is more reliable, but rather something that is more tolerant of sloppy programming.

Personally, I'd like to see SKS re-implemented in C.


------------------------------------------------------------------------

_______________________________________________
Sks-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/sks-devel

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Sks-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/sks-devel

Reply via email to