vscode-db2i
vscode-db2i copied to clipboard
halcyon-tech
Db2 for IBM i Tools for VS Code
It appears as-if the current library is being pre-pended to the user library list when starting a SQL job. As a result, the setting of the library list fails CPF2184....
```sql -- -- MTIs that exist for a specific file -- with mtis(keys, KEY_DEFINITION, MTI_SIZE, LAST_BUILD_START_TIME, LAST_BUILD_END_TIME) as ( select keys, KEY_DEFINITION, max(MTI_SIZE), max(LAST_BUILD_START_TIME), max(LAST_BUILD_END_TIME) from table ( qsys2.mti_info(TABLE_SCHEMA =>...
When you expand an error in SELF and see the job id, it'd be cool to have a button to show the job log for it.
Chat AI
* [x] merge missing changes from main * [x] update vscode requirement to 1.90 in package.json * [ ] finalise db2i chat commands * [ ] liam to cleanup build...
because the command+option+f shortcut is a pain
Addresses #240 TODO: - Add command to Run Dialog to open Data Preview - review `preview` logic - add data preview extension as dependency, or check if the extension exists...
## render tables with vscode-data-table extension - https://github.com/RandomFractals/vscode-data-table  Column stats:  
Putting this here to see if this is a good idea or not. ## Idea Add a `preview` statement qualifier that can open up the result set using the Data...
Trace ``` [DATASTREAM_IN]: 2024-06-07.07.27.08.964 {"id":"id2","type":"connect","technique":"tcp","application":"vscode-db2i 1.0.0-dev","props":"libraries=SCHINDLN,QTEMP,OBJEKTTEST,DATEIEN,OBJEKTE,NEWSCAN,QGDDM,QIDU,QGPL,AUFTRAG,VERKAUF,EINKAUF,TAATOOL,ARCHIVP,GSESPL,E3SXROSS,E3SIROSS,SYSADMIN,SOURCEN,PROFOUNDUI,PROFOUNDJS,ILEASTIC,ILELDAP,ILEVATOR;naming=system;full open=false;transaction isolation=none;query optimize goal=1;block size=512;selfcodes=*NONE"} [DATASTREAM_IN]: 2024-06-07.07.27.17.291 {"id":"id3","type":"setconfig","tracedest":"IN_MEM","tracelevel":"DATASTREAM"} [DATASTREAM_OUT]: 2024-06-07.07.27.17.296 {"id":"id3","tracedest":"IN_MEM","tracelevel":"DATASTREAM","jtopentracedest":"IN_MEM","jtopentracelevel":"OFF","success":true} [DATASTREAM_IN]: 2024-06-07.07.27.20.017 {"id":"query4","type":"sql","sql":"select * from qsys2.sysfuncs","terse":true,"rows":100} [INFO]: 2024-06-07.07.27.20.017 asynchronously dispatcing a request of...
Right now, it uses a like statement. We'd like to be able to do a generic name in the search box, for example: `a*`. Also would be nice to support...