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
Copy file name to clipboardExpand all lines: README.md
+42-48Lines changed: 42 additions & 48 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -149,7 +149,7 @@ To execute a q file in REPL:
149
149
150
150
The results are shown in the terminal and you can continue to work either in your q file or directly in the terminal.
151
151
152
-
Refer to the [REPL shortcuts table](https://github.com/KxSystems/kx-vscode/wiki/REPL) for information on the keyboard shortcuts you can use.
152
+
Refer to the [REPL shortcuts table](https://github.com/KxSystems/kx-vscode/wiki/Reference-Card#repl) for information on the keyboard shortcuts you can use.
153
153
154
154
### Benefits of using REPL
155
155
@@ -177,11 +177,11 @@ Refer to the [PyKX within REPL](https://github.com/KxSystems/kx-vscode/wiki/Use-
177
177
178
178
### Supported file types
179
179
180
-
In addition to q and Python files, SQL files are also supported for execution within REPL. Refer to the [supported execution types](https://github.com/KxSystems/kx-vscode/wiki/Supported-Execution-Types) table for more details.
180
+
In addition to q and Python files, SQL files are also supported for execution within REPL. Refer to the [supported execution types](https://github.com/KxSystems/kx-vscode/wiki/Reference-Card#execution) table for more details.
181
181
182
182
## Connections
183
183
184
-
The **kdb VS Code extension** allows you to have multiple connections open at once, enabling development and testing across different KDB-X and kdb Insights Enterprise connections using both q and Python.
184
+
The **kdb VS Code extension** allows you to have multiple connections open at once, enabling development and testing across different KDB-X and kdb Insights Enterprise connections using q, Python, and SQL.
185
185
186
186
To add connections:
187
187
@@ -213,8 +213,6 @@ Set the following properties:
213
213
| Enable TLS Encryption | Check the box is TLS is enabled. Learn more [about TLS encryption](https://code.kx.com/q/kb/ssl/). |
214
214
| Label Name | Select the label you want to assign the connection to |
1. Click **Create Connection** and the connection appears under **CONNECTIONS** in the primary sidebar.
219
217
220
218
1. Right-click the my q process listed under **CONNECTIONS**, and click **Connect server**. This connects to the child q process running inside the kdb VS Code extension.
@@ -233,8 +231,6 @@ Set the following properties:
233
231
| The connection address | This is the remote address of your **kdb Insights Enterprise** deployment: e.g. `https://mykdbinsights.cloudapp.azure.com`|
234
232
| Label Name | Select the label you want to assign the connection to |
1. The kdb VS Code extension runs an authentication step with the remote **kdb Insights Enterprise** process to sign-in.
255
251
@@ -281,8 +277,6 @@ To edit an existing connection, right-click the connection you wish to edit and
281
277
282
278
> NOTE: Editing an **active connection** may require you to **restart** the connection. If so, you are prompted to reconnect after saving your changes.
When editing a **My q** connection, you can edit the following properties:
@@ -470,8 +464,6 @@ For any file with a **.q** or **.py** extension there are additional options ava
470
464
471
465
-**Execute current block** - Selects the q expression under the cursor and executes it against the active connection. Results are displayed in the [Output window and/or the KDB Results window](#view-results).
472
466
473
-
-**Run q file in new q instance** - If q is installed and executable from the terminal you can execute an entire q script on a newly launched q instance. Executing a file on a new instance is done in the terminal, and allows interrogation of the active q process from the terminal window.
474
-
475
467
When executing Python code against kdb+ connections, **note** the following:
476
468
477
469
- A Python variable is defined in the remote process `_kx_execution_context`, which means you need to explicitly accept it to avoid implicit changes to the remote process. It doesn’t make any other change to the remote process.
@@ -797,7 +789,7 @@ KX Notebooks detect [GGPlot2](#grammar-of-graphics) outputs. If the execution ge
Sample notebooks are available on [Developer Wiki](https://github.com/KxSystems/kx-vscode/wiki/Sample-KX-Notebooks).
792
+
See the [Sample KX Notebooks](hhttps://github.com/KxSystems/kx-vscode/wiki/Sample-KX-Notebooks) for more detailed examples.
801
793
802
794
## Query History
803
795
@@ -829,8 +821,6 @@ All query executions happen remotely from the **kdb VS Code extension** either a
829
821
830
822
-**Output** - The **Output** window displays results as they are received by the **kdb VS Code extension**. It includes the query executed, a timestamp and the results.
**Note:** You can enable/disable auto-scrolling in the VS Code settings. This setting determines whether the output view scrolls to the latest results.
|**Hide notification for installation path, after first install**| yes/no; default no |
895
-
|**Hide subscribe for registration notification**| yes/no; default no|
896
-
|**Hide the extension survey dialog box**| yes/no; default no|
884
+
|**Automatically [focus the output](#auto-focus-output-on-entry) console when running a query without an active results tab or receive log entry**| yes/no; default yes|
885
+
|**List of label names and color set**| edit JSON settings|
886
+
|**Connection map for workspace files**| edit JSON settings|
0 commit comments