281–290 of 433 posts
Earlier quoted context omitted.
SSMS is also for Development, I've been using it for that for 20 years
Same here, much better than the VS tooling for SQL Server, including all the Transact-SQL support.
https://learn.microsoft.com/en-us/archive/msdn-magazine/2005...
This solves a major problem that I built an npm package called "pgstrap"[1] for. It generates a "database structure" directory so that my database schema is available to LLMs (it also makes code review easier because you can see the changes to various tables). So I have a SQL file for each table in my database, neatly organized into directories for each schema. Rails has a similar idea with schema.rb I'm not sure whe…
I’m confused. Isn’t including the canonical state of the database schema in version control along with all the migrations that brought it to that point a completely standard part of every web framework?
Earlier quoted context omitted.
Because of the closed extensions situation, the open source part feels insincere. Sort of like a free plan up to 10 users and then pretty expensive situation. The purpose isn't the free plan, it's just an advertising measure to get people to where you really benefit eventually.
You're mixing up ideas. Microsoft isn't "sincere" because it's just a business doing what businesses do, making money. They're not trying to be altruistic or principled. They're just doing business. But I have personally benefited from this deal by having TypeScript and VS Code at my disposal.
Earlier quoted context omitted.
I just use a MCP server (with copilot or cline) that has a read only login to my database.
Which is strictly worse than just giving the LLM access to the source of truth for the database. You're adding a round trip to the database and the LLM and inserting a tool call in the conversation before it even starts generating any code. And the reference Postgres MCP implementation doesn't include Postgres types or materialized views, and is one of the most widely used packages: Zed.dev's MCP server for example,…
This solves a major problem that I built an npm package called "pgstrap"[1] for. It generates a "database structure" directory so that my database schema is available to LLMs (it also makes code review easier because you can see the changes to various tables). So I have a SQL file for each table in my database, neatly organized into directories for each schema. Rails has a similar idea with schema.rb I'm not sure whe…
I’m confused. Isn’t including the canonical state of the database schema in version control along with all the migrations that brought it to that point a completely standard part of every web framework?
Oh 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.
There is already a Microsoft SQL server extension for VS Code and this looks to effectively be a clone of it. After giving this a quick spin, it looks and feels the same as the SQL server extension, with the same menus, dialogs, etc. The SQL server extension I believe is what formed the basis of the now-deprecated Azure Data Studio (which was a VS code fork). See here for the SQL server extension: https://marketplace…
Earlier quoted context omitted.
They already have the SQL Server Management Studio[1], which seems to cover similar ground? I'm assuming they might want to move SSMS to VSCode in time, so trying it out by covering new ground, PostgreSQL, makes sense to me. [1]: https://learn.microsoft.com/en-us/ssms/sql-server-management...
No, it has a different purpose; VS Code extension and the former ADS are targeted for development, while SSMS is for server and database administration. I am a heavy user of SSMS and can do everything I ever need there, I don't use the VS Code extension for MS SQL even if I have it installed and I use VS Code quite a lot. This is because I am also acting as a backup and supervisor for our DBA team, so I am involved i…
Earlier quoted context omitted.
Because of the closed extensions situation, the open source part feels insincere. Sort of like a free plan up to 10 users and then pretty expensive situation. The purpose isn't the free plan, it's just an advertising measure to get people to where you really benefit eventually.
I recently called this (and other Microsoft behavior) out as being "fake" open source. The comment was highly controversial with quite a battle of up and down votes - so clearly not everyone agrees. In my opinion, Microsoft wants the good vibes and PR that comes with open source, but they don't actually want to be open source. Its why many people still don't trust them in this arena.
Earlier quoted context omitted.
Same here, much better than the VS tooling for SQL Server, including all the Transact-SQL support.
I still miss the tool it replaced, SQL Query Analyzer/Profiler. To this day it's my favourite SQL 'IDE'. https://learn.microsoft.com/en-us/archive/msdn-magazine/2005...
Earlier quoted context omitted.
I've found Datagrip to be far and away the most impressive universal database tool. I feel like I've tried them all, and they all have a quality of having been developed by database people, rather than IDE designers. The depth of capability, extensibility, pace of improvement--I'm a very happy customer. I don't want to poop on open source, but pgadmin and dbeaver and not even close to playing in the same league. I wo…
Are there any features in datagrip in particular that you like that aren't in dbeaver?
In my experience, DataGrip has been easier to get up and running out of the box and bringing the big IDE guns than DBeaver but DBeaver also does done this really well. For example I have never been able to setup DG with Access but DBeaver works pretty good out of the box with that garbage. Also it's free.
Both are solid