ged-yuko

Results 23 comments of ged-yuko

@camalolo your case is different, you really have such a column but it was not resolved for some reason. The error produced by the column name against table data context...

I tried to repeat your steps and fail to see how it uses port number from the grayed field, when URL switch is checked. For me it uses port from...

@edwin-hendriks let me try to elaborate with a bit of educated assumptions according to my understanding of PgPass: - As far as i understand, Postgresql JDBC connection driver, used by...

Also try to resize the window, switch perspective to the other one and back. It might be a toolbar rendering glitch, so resize would trigger it to relayout itself and...

DBeaver doesn't support such a syntax in its semantic analysis engine apparently at the moment. See parser [specification](https://github.com/dbeaver/dbeaver/blob/4c6d1915cf13ae2671591fb01889b5a2d895e94a/plugins/org.jkiss.dbeaver.model.lsm/grammar/SQLStandardParser.g4#L403) for the details. I would propose to make it a feature request.

The reason is that DBeaver doesn't allow you to choose active schema in the main toolbar for the current SQL Editor. Autocompletion just uses known active db object context to...

> the full command would never actually be sent to the SQLite engine. There is a workaround actually: you can manually select a whole text fragment containing SQL statement and...

Looking at the case where completion engine handles [qualified object name accomplishment](https://github.com/dbeaver/dbeaver/blob/8133cf5fc23621698ea9bf98279b6585528b7714/plugins/org.jkiss.dbeaver.model.sql/src/org/jkiss/dbeaver/model/sql/semantics/completion/SQLQueryCompletionContext.java#L447) (when there is a prefix resolved to a schema for example), and a case of [non-prefixed table name...

@romiof according to the original poster's answer [here](https://github.com/dbeaver/dbeaver/issues/38883#issuecomment-3173453015) he cannot even observe synonyms **with** the schema prefix. This is why this issue was open still, even though literally the [next...

Looking at the [SQLStandardParser.g4](https://github.com/dbeaver/dbeaver/blob/devel/plugins/org.jkiss.dbeaver.model.lsm/grammar/SQLStandardParser.g4), PIVOT clause is not supported yet.