You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think this is a matter of choice if we are aiming to replace KDB Studio. We need to follow its overall design principles, which includes that the server connection only needs to be alive if you actually want to do any queries. Many users have loads of different servers with no good choice for one to use as the "default". Also these servers may keep coming up and down. So locking the editor behind having to open a server connection would be a hindrance in terms of UX.
Updates as discussed between @gyorokpeter and @ColinEberhardt during KDB meeting finos/kdb#59. There should be a local config to disable communications to external servers where this can be a banking infrastructure concern.
No description provided.
The text was updated successfully, but these errors were encountered: