On Oct 20, 2008, at 9:32 PM, C. Titus Brown wrote:
> Yes, but replace it with what... is sqlite the answer? One obvious category is write-once, read-many applications, which constitute almost all of our typical Pygr applications (seqdb indexing, NLMSA ID lookup table, etc.). Here all we need to do is save a sorted file and have a fast way of binary searching it without having to load more than a fraction into memory. What you and Alex wrote for seqdb2 is an example of this kind of function. And of course, we can also use sqlite. In general, I think we should have more than one backend because no one back-end will necessarily solve all problems optimally. At any rate, I am heartily sick of bsddb; both the hash and btree indexes seem to have serious scalability problems. -- Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
