<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 24, 2010, at 12:15 PM, Shane Kerr wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>All,<br><br>Interesting comment on the BIND 10 blog today:<br><br><a href="https://www.isc.org/community/blog/201004/why-sqlite3#comment-510">https://www.isc.org/community/blog/201004/why-sqlite3#comment-510</a><br><br> Comment by Gregory Burd (not verified) on 23 Jun 2010 <br><br> We here in the Berkeley DB group within Oracle would be happy to<br> support your testing efforts comparing BDB SQL(ite) with native<br> SQLite. I'm fairly confident that you'll see a dramatic<br> difference in concurrency, throughput and query execution time.<br> This, to me, seems like a great way to provide value to those<br> who use BIND10 with the minimal effort. A configuration-time<br> switch to choose BDB SQL(ite) or native SQLite would provide<br> your customers with an easy way to improve performance and help<br> you avoid all that custom engineering to improve performance by<br> working around SQLite restrictions (using multiple database<br> files for instance). Please contact me if you'd like to do this<br> work with us.<br><br> regards, and thanks for your hard work,<br><br> -greg<br><br>I think that's very cool, since I was hoping for BDB support in the next<br>3 months. :)<br></div></blockquote><div><br></div><div>Could not agree more! So, get to work! :)</div><div><br></div><div>Don't hesitate to ask if you need input from me regarding using BDB with the DLZ library in older versions of Bind (if that can be of any help at all). </div><div><br></div><div>Regards,</div><div>LG</div><br><blockquote type="cite"><div><br>--<br>Shane<br><br>_______________________________________________<br>bind10-dev mailing list<br><a href="mailto:bind10-dev@lists.isc.org">bind10-dev@lists.isc.org</a><br>https://lists.isc.org/mailman/listinfo/bind10-dev<br></div></blockquote></div><br></body></html>