Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
IntelliJ Plugin: Postgres: Attribute not found
See original GitHub issueSQLDelight Version
1.5.3
IDE Version
IntelliJ 2021.3
Dialect
PostgreSQL
Describe the Bug
If using dialect = "postgresql", the Intellij plugin is not able to find the table definition and marks all attributes as not found.
reproducer project: postgresql.zip
Stacktrace
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:8
Top Results From Across the Web
PostgreSQL | IntelliJ IDEA Documentation - JetBrains
At the bottom of the data source settings area, click the Download missing driver files link. As you click this link, IntelliJ IDEA ......
Read more >PostgreSQL showing tables problem
I'm using 'postgres' user. It's no error message to understand what is the problem. Every other SQL server that I use is OK....
Read more >Class not found exception using SSL on Postgres DB
I have started getting the following expception when trying to connect to one of our databases which uses SSL... [08006] SSL error:...
Read more >Cannot connect to a database | IntelliJ IDEA Documentation
Check your connection properties. Each database (MySQL, PostgreSQL, Oracle, or any other vendor) has its own connection settings.
Read more >PostgreSQL 12: Error while browsing the database tree
I Had the same issue with Intellij 2019.1.1, but i fixed it enabling the option: "Introspect using JDBC metadata" !
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
it could be, sometimes intellij APIs change and break out existing behavior.
closing out cause we changed how dialects work in general