https://bugs.documentfoundation.org/show_bug.cgi?id=156471
--- Comment #4 from Lionel Elie Mamane <lio...@mamane.lu> --- (In reply to prrvchr from comment #2) > Could we not consider that all urls starting with: sdbc:embedded are managed > as embedded databases. I don't understand what you want to happen exactly technically where. I mean, as a policy, I would certainly "encourage" (if not __require__ on a policy level to accept the patch) any driver to use URIs like sdbc:embedded:foo only for embedded databases (!) and vice versa. But if you want to enforce that technically, I don't see how, and in theory I think it is not possible: we would have to "inspect" the driver code (automatically) to see where it writes the actual database data (is it in the odb file or elsewhere?). That would inter alia solve the halting problem :) (In theory, we could apply some heuristics to guess, but... why? and what when the guess is wrong?) > After the installed drivers do the job... Well, the current system is that drivers register the URI patterns (usually prefixes...) they are able to manage, and LibreOffice starts (and delegates work) to the driver that has registered to manage the URI that the odb file is configured with. So any driver that manages any sdbc:embedded:XXXXXX for any value of XXXXXX will register that URI prefix. So given an odb file configured with URI sdbc:embedded:foobar or sdbc:embedded:foobar:qux or sdbc:embedded:foobar?qux or ..., either there is a driver that manages it and it will work or there is not, and the user will get an error message along the lines of "no driver for sdbc:embedded:foobar". -- You are receiving this mail because: You are the assignee for the bug.