On Mon, Oct 27, 2014 at 3:17 PM, Stephan Beal <sgb...@googlemail.com> wrote:
> That's conceptually the same problem we're trying to solve here: keep the
> public db names stable, regardless of where/how they're actually attached.

Yes, I think that's desirable.

If it's not too much to ask for then SQLite3 ought to: a) check for
duplicates by canonicalized path (but keep in mind that this can be
difficult to do portably, or without obnoxious length limitations on
Windows), then b) check for duplicates by st_dev/st_ino where

sqlite-users mailing list

Reply via email to