Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Postgres IDE in VS Code

techcommunity.microsoft.com

Post reply on HN
Print view View original

291–300 of 433 posts

Re: Postgres IDE in VS Code

#291

Post by sbuttgereit »

AdrianB1 wrote: post #219
qntmfred wrote: post #24

will 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…

In my experience most SQL developers don't care too much about tooling. In most cases someone designs the database and tables, developers don't care about databases and care mostly about tables and views, rarely about indexes. The ones that care, and need tooling, are usually called development DBAs and they are very rare. Rare enough I was never able to hire one and keep them (we don't pay enough for how rare they a…

I've been in that camp for much of my career, and yes, tooling matters.

As you suggest however, tooling for that workload is pretty rare. I want something that focuses on enhancing the database development experience: that understands that there are development workflows for database code which are well controlled and rigorous. So many database tools are focused on being system administrative aids first, or giving you features for directly interacting and altering the running state of the database and its server from the tool.

The best tool I found for what I do was targeted at Oracle: Allround Automation's PL/SQL Developer (https://www.allroundautomations.com/products/pl-sql-develope...). It's a development oriented tool that, at least last I used it, was focused on serious development work rather than administrative work. Now, I haven't used it in almost 20 years when last I did Oracle development... but I haven't found anything for PostgreSQL that has that thoughtfully implemented database developer centric feature set.

Today I muddle through with DataGrip. DataGrip has just enough of what I need that it's marginally better to work with than just a simple text editor... and also narrowly avoids some misfeatures as not to negate it's utility.

Re: Postgres IDE in VS Code

#292

Post by cerved »

Ericson2314 wrote: post #184

Microsoft Access meets PostgreSQL, 3 decades later?

Is there something related to Access in this that I missed in this or you just being salty, because I have to work with that garbage and if there's something better than DBeaver I can use for that I'm all ears

Re: Postgres IDE in VS Code

#293

Post by cerved »

gregd wrote: post #116
J_McQuade wrote: post #87

Earlier quoted context omitted.

Easily VSCode, if we're talking about developer reach. I'm not big into Microsoft stuff, but almost every 'serious' .Net developer I personally know is using Rider, so I can only assume that Visual Studio is retreating to the same space occupied by Eclipse and Netbeans, i.e. still used, but mostly only in places where change is hard. I'm an emacs user and even I keep a copy of VSCode installed just because I occasion…

I only use Rider because it's cross-platform. It's not inherently better (or worse) than Visual Studio with Resharper installed.

it's fasterb and has a functional vim interface

Re: Postgres IDE in VS Code

#294

Post by tomnipotent »

ahartmetz wrote: post #283
90s_dev wrote: post #190

Earlier quoted context omitted.

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.

I don't believe that all business is "just business". You have tobacco companies and Purdue Pharma on one end of the spectrum and, let's say, Mozilla Corporation and Valve (debatable but I think they're cool) on the other end. And, of course, large companies are kinda many different entities, really. Microsoft has a long history of dishonest behavior, some of it pretty sophisticated and with a long-term view. That ma…

> Microsoft has a long history of dishonest behavior

Can you point out such recent behavior that isn't just echoing other peoples opinions from the anti-trust case from over two decades ago? It's been my experience that many people seem to "borrow" their opinion about Microsoft from things they've read rather than personal experience so we keep getting the same low-effort criticism ad nauseam.

Re: Postgres IDE in VS Code

#295

Post by sbarre »

wredcoll wrote: post #282
semiquaver wrote: post #278

Earlier quoted context omitted.

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?

That "works" for about as long as you have <10 employees and <3 customers or so. After that the railsapp doesn't get to be the sole owner of the db.

Do you have multiple separate apps that can change a shared DB schema?

How do you keep that all in sync across your apps?

Re: Postgres IDE in VS Code

#296

Post by layoric »

maxluk wrote: post #275
layoric wrote: post #269

Earlier quoted context omitted.

Thanks. I worry about these kind of tools connecting to production databases.. Especially considering how easy it is to switch out LLM endpoints, where that data is going, how it is retained, the context etc becomes a bit of a privacy nightmare..

Absolutely valid concern. Our extension connects to LLMs through Github Copilot. Github Copilot is Microsoft product and offers variety of enterprise plans, which enables your IT to approve what can be used for what kind of data. This gives you a clear path towards compliance with your enterprise requirements.

Makes sense. Appreciate the responses. Honestly though, as a person outside the US, I'm removing my dependence on US company IT tools and infrastructure, GitHub, VSCode, AWS etc, enterprise or otherwise.. Congrats on the project though.

Re: Postgres IDE in VS Code

#297

Post by lossyrob »

dmurray wrote: post #208
lossyrob wrote: post #182

Earlier quoted context omitted.

We're working the details out right now, but the change will make it clear that the extension has a free license without restrictions. Stay tuned!

You're a dev on the project and consider yourself authorized to speak on behalf of the project, on a legal matter, on Hacker News. Are you authorized to do the same on a blog hosted on microsoft.com? A lot of people would treat that as authoritative even if bigger enterprises will wait for the shrink-wrap to be updated.

The blog has been updated, see the section "Feedback and Support".

Re: Postgres IDE in VS Code

#299

Post by MonkeyClub »

getgalaxy wrote: post #65

Super cool for them to finally add in VSCode. My team is trying to build even more here by building a dedicated SQL editor with a context aware AI copilot, and with sharing and collaboration so we don’t need to send queries in slack anymore :) Check it out and get on the waitlist getgalaxy.io/explore/product-tour happy to chat live with anyone if interested, support@getgalaxy.io

Your whole comment history seems to be spamming for your app.

Not a good way to generate potential user interest or generally good feelings towards it.

Just saying.

Re: Postgres IDE in VS Code

#300

Post by xyzzy123 »

semiquaver wrote: post #278
seveibar wrote: post #77

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?

It often is, but the schema might be written against a language-specific ORM.

That code might in turn have plugins or feature flags that mean you don't know the concrete sql schema until runtime.

Same for seed data and migrations.

So it depends on the use-case how useful this format is for tooling and discovery vs an actual connection to the database.

Post reply on HN