dbeaver / dbeaver/dbeaver

ContentAssistant does work right with real Ibmi-DB2 SQL-Tables (metadatasource=0/1 and naming=system)

Open
#12,216 4 comments 0 reactions 0 assignees View on GitHub
x:db2i xf:sql autocompletion
Dominant language
Java
Stars
51.8k
Forks
4.4k
Avg merge
3d 8h
Merged PRs (30d)
188

Description

#### System information:
- Operating system (distribution) and version === Microsoft Windows 10 Enterprise - Version 10.0.19042 Build 19042
- DBeaver version === Version 21.0.3.202104181339 - Released 19 April 2021
- Additional extensions === NO, standalone DBeaver instance - Same behaviour in the Eclipse IDE.

#### Connection specification:
- Database name and version === Ibmi DB2 V7R4 - Latest TR
- Driver name === DB2 iSeries/AS 400 - net.sf.jt400:jt400:RELEASE - Version 10.6
- Do you use tunnels or proxies (SSH, SOCKS, etc) === NO

#### Describe the problem you're observing:
* DBeaver is really a **very very good tool** to work with databases. **Many thanks !**

* I read thru the docs and issues, but did not see what I'm doing wrong.

* I would like to actively contribute to find solutions/document/test because we are currently moving to 'real' SQL-Tables instead of PFs and LFs (legacy physical and logical files) and the issues have mostly to do with these new tables.

* I can use the Ibmi system I develop on to carry out tests. I cloned the repo to start debugging.

* I think all the issues have to do with these driver settings :
* naming="system" meaning that the DB-objects are searched in a list of schemas (Libraries) instead of only the one set with SET SCHEMA
* metadatasource="0" (Retrieve Object Information) or "1" (SQL stored procedures) or "-1" (??)

* Just wanna give an overview of the issues here. I can split them apart later on into separate bugReports for easier handling and supply more details.

* Issue 1 : Table properties do not show ANY columns for real SQL-Tables :
* ![image](https://user-images.githubusercontent.com/55274187/115739859-94ad4900-a38e-11eb-9c46-608e6e2fe41e.png)
* Note that an SQL-Script shows the right metadata
![image](https://user-images.githubusercontent.com/55274187/115742163-b6a7cb00-a390-11eb-8125-27af731d35d0.png)

* Issue 2 : Table properties for legacy PFs do not show column descriptions when metadatasource="1"
* ![image](https://user-images.githubusercontent.com/55274187/115738831-b65a0080-a38d-11eb-9cf7-beb1737cc4d2.png)
* ![image](https://user-images.githubusercontent.com/55274187/115739417-34b6a280-a38e-11eb-89f9-03b96dbc5086.png)

* Issue 3 : Content assistant in SQL script does only find tables when a schema is set (is against naming=system)

* ![image](https://user-images.githubusercontent.com/55274187/115741354-f3bf8d80-a38f-11eb-8004-e57e30f80553.png)
* ![image](https://user-images.githubusercontent.com/55274187/115741834-629ce680-a390-11eb-9ae8-3c382584bc71.png)

* Issue 4 : Content assistant in SQL script does not show columns for real SQL-Tables

* does not show for real SQL-Tables
![image](https://user-images.githubusercontent.com/55274187/115742994-80b71680-a391-11eb-90f4-8c44cde2924c.png)

* does show right for legacy PFs
![image](https://user-images.githubusercontent.com/55274187/115743588-18b50000-a392-11eb-9a9f-34eb47b0effa.png)

#### Steps to reproduce, if exist:

#### Include any warning/errors/backtraces from the logs

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.