Date: prev next · Thread: first prev next last
August 2019 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=125331

--- Comment #6 from Lionel Elie Mamane <lionel@mamane.lu> ---
(In reply to Heiko Tietze from comment #5)
(In reply to Lionel Elie Mamane from comment #4)
I have no simple idea to enhance it.

What do you think about my idea to gray-out those entries where the data is
(temporarily) not available?

By data, you mean the actual data, not the .odb file. How do you determine
that? You can't just try to connect:
 - can take network requests, time (large list), consume client licence spot on
SQL server, ...
 - you may be missing a password; you will not ask the password of all
entries(!). How will you reliably determine if the connection failed 
You want to limit it to non-network requests? You will still need to open each
.odb file, see what it connects to (embedded data? network database? another
data file?) and make a decision. Also not good for performance, a file can also
be on a slow NAS / network filesystem over a VPN over slow Internet, ...

If you mean checking whether the .odb file is reachable, that can work, and I
would not oppose the patch. Not sure users will understand the difference
between the odb and the data, but <shrug>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.