Biggest thing that JetBrains has over VSCode for me was their very clean built in database tooling
Postgres IDE in VS Code
21–30 of 433 posts
Re: Postgres IDE in VS Code
#22Re: Postgres IDE in VS Code
#23I still think Jetbrains has the gold standard in IDE - Database interaction
Interesting in knowing why you think that
Because of a rich feature set and amazing integration with DB providers.
Good starting point: https://www.jetbrains.com/pages/intellij-idea-databases/
Re: Postgres IDE in VS Code
#24will definitely be taking a look at this. i started my career on mostly SQL Server and using SSMS fits my brain like a glove. i've been so dissatisfied with the typical options (pgadmin, dbeaver, datagrip, etc) for managing/querying postgres since i started using it probably like 10 years ago. postgres itself is great (don't get it twisted either, SQL Server is fantastic. just costs money) but i never understood why there wasn't more uproar in the community about its DBMS tooling ecosystem
Re: Postgres IDE in VS Code
#25I'm sure nobody cares, but I just independently stumbled upon this an hour ago and wondered why more people haven't used it.
Re: Postgres IDE in VS Code
#26Oh woah this looks great. Quite amazing they put the effort into this for Postgres instead of SQL Server. The demand must be a lot higher.
I speculate that it's because the MSSQL tools have been maintained as part of Azure Data Studio, and were in better shape.
ADS is being sunset, and I was surprised when trying to install the Postgres extension on VS Code to find that it had its last meaningful contribution 6 years ago [0]. It couldn't work on newer VS Code versions.
I use ADS with both Postgres and MSSQL, prior to this announcement, I kept using ADS because there was nothing to migrate to.
[0] https://github.com/microsoft/vscode-postgresql/commits/maste...
Re: Postgres IDE in VS Code
#27It has a proprietary license[0]. That makes it a non-starter. Too bad: it looks nifty!
> The software is licensed, not sold. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you will not (and have no right to):[…] d) use the software for commercial, non-profit, or revenue-generating activities
Oops. Better not install this on your work laptop!
[0] https://marketplace.visualstudio.com/items/ms-ossdata.vscode...
Re: Postgres IDE in VS Code
#28> [...] all without ever leaving your favorite code editor. That's cool. How do I get this into JetBrains IDEs?
This is Microsoft catching up to what JetBrains has had all along (in their paid products). There's DataGrip but I was also using all these features (minus the AI stuff) in IntelliJ Ultimate and PyCharm 5+ years ago.
The main difference is that JetBrains supports a bunch of databases, not just one.
Re: Postgres IDE in VS Code
#29I still think Jetbrains has the gold standard in IDE - Database interaction
I've been using DataGrip for a few weeks and admit it is a nice upgrade to DBVisualizer that I've been using for 10 years. The intellisense and features like being able to select the query in the current window are big time savers for me. I'm still on a trial and not certain I'll purchase it just because things are moving so fast in this field. I feel like not having it in my VSCode Agent loop is a huge negative at this point
Re: Postgres IDE in VS Code
#30Oh woah this looks great. Quite amazing they put the effort into this for Postgres instead of SQL Server. The demand must be a lot higher.
I speculate that it's because the MSSQL tools have been maintained as part of Azure Data Studio, and were in better shape. ADS is being sunset, and I was surprised when trying to install the Postgres extension on VS Code to find that it had its last meaningful contribution 6 years ago [0]. It couldn't work on newer VS Code versions. I use ADS with both Postgres and MSSQL, prior to this announcement, I kept using ADS…
They built the postgres plugin in a way that nobody could usefully contribute to unless they worked at msft - like the rest of ADS the level of control they tried to maintain meant nobody wanted to work on it.