Disable fetching all schemas? #18
Comments
|
Oracle's slow schema retrieval is a known issue. One thing that might help is to edit the connection's "Advanced" properties and change the "restrictGetTables" property from "false" to "true". That may reduce the number of schemas that are returned. Other than that, we don't currently have a good way to restrict the schemas that are queried when you first connect, but you can hide the schema items that you aren't interested in seeing by selecting all the schema/table items and right-clicking to see the "Hide Item(s)" menu item, which will prevent the undesired schema items from being displayed. If you want to see the hidden items again later, you can select "View"/"Display Hidden Items". Please let us know if this helps your scenario or not. |
|
Hey Marc, thanks for your super quick reply! The "restrictGetTables" property does not seem to make a difference. I followed your advice hiding the schemas I'm not interested in and it works as expected, giving me a pleasantly snappy UI, thanks! |
|
In case it is of any help, here's a snippet I copied from Apple's crash reporter: |
|
Thanks for the debug info. If the app ever comes back after the hang, are the schemas successfully hidden? And if you then "show hidden items", do they appear again? |
|
I gave it another shot, but it's been completely stuck for the past 10 minutes … |
|
We're working on the performance issue and we will be issuing an update within the next few days. For the time being, your best bet is to delete the .splice file and create a new one and no hide the schemas for the Oracle connection. Once the update is released on the App Store, you should be able to go back to hiding the schemas. Out of curiosity, about how many schemas are we talking about? Dozens, or hundreds? |
|
Release 1.1.1 should be available now. Can you try it out and see if it help address your issue? |
|
I‘ll definitely give it another shot at work tomorrow!
Oh, and yes, it really ist more like hundreds of schemas.
What seems to stop (for example) DBeaver from freezing is that it only shows schemas which I actually can access, grants-wise.
… On 7. Nov 2018, at 16:25, marcprux ***@***.***> wrote:
Release 1.1.1 should be available now. Can you try it out and see if it help address your issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Did you manage to test this out? We're also working on a new release that provides some more performance improvements to schema fetching and hiding. |
|
Ah, sorry Marc, I wanted to reply earlier but it slipped my mind before I got around to it. I tried it again with But no luck, still hangs. Let me know if I can help you out with more data :) |
Hi!
I'm just trying out splice for work.
We have a bunch of Oracle servers and each server is pre-configured with a bunch of enumerated schemas for each developer (think
username01throughusername20).When connecting to one of those servers, Splice fetches all of these schemas giving me a list of a couple hundred items in the outline (of which I can only access the one matching my username) and freezing Splice for about a minute.
Since this is related to the way we set up our database server I guess there won't be a one-size-fits-all solution.
Is there a way to filter the schemas when setting up the connection? Maybe some advanced config option I don't know of?
The text was updated successfully, but these errors were encountered: