On Mon, Aug 9, 2010 at 9:57 PM, Jeremy Orlow <jor...@chromium.org> wrote: > I'm pretty sure opening a database with a different description is actually > already specified: the new one takes precedent. Take a look at the > algorithm for database opening; I'm pretty sure it's there. > When talking to Andrei earlier tonight I thought we'd probably want to make > it optional, but now I'm thinking maybe we shouldn't. You're right, Shawn, > that the description can be useful for many reasons. And although it seems > redundant for a developer to pass in the description every time, I actually > can't think of any reason why a developer wouldn't want to.
Actually, I think it's pretty inconvenient to have to specify a description every time, especially since I am not sure developers would want to change the description very often. I think we should allow a null string for future connections as Shawn suggested. Thanks, Andrei
