3 ms·

Wow, you must've been trying hard to cherry pick those. I'm actually curious about this one: >SSMS is an unusable hog. There is just no nice way to put it. I

by fhery 7y ago

Wow, you must've been trying hard to cherry pick those. I'm actually curious about this one: >SSMS is an unusable hog. There is just no nice way to put it. I've been using both postgre and sql server for like 1.5 year and tooling difference between pgAdmin and SSMS is insane SSMS is mature, reliable and makes my life easier meanwhile pgAdmin is just viable, but nothing more. Generally SQL Server seems to be years ahead in compare to postgre when it comes to features/tooling. I also used mysql via xamp and sql management in compare to all of those is world class >NuGet constantly fails silently when trying to restore packages. what?

juststeve 7y ago
When you type Install-Package in Visual Studio, sometimes it just fails to find the package at all. You have to search for it first, then type Install-Package, and then it actually downloads etc.
- fhery 7y ago
  I'm always doing it via Nuget Package Manager and I don't remember having any troubles with that I'm using dotnet's CLI mostly for migrations/publishing
  - juststeve 7y ago
    Yeah i think package manager GUI is ok? but cli and powershell, not so much
Nullabillity 7y ago
> Wow, you must've been trying hard to cherry pick those. Not really. Just try keeping a .NET/MSSQL environment running for a few days, and the stories will build up quickly. > SSMS is mature, reliable and makes my life easier meanwhile pgAdmin is just viable, but nothing more. But psql is good enough that I pretty much never have to touch pgAdmin. And for ad-hoc editing (the only case where graphical editors have any real advantage), surprise, SSMS can't edit the results of custom queries. pgAdmin doesn't care, as long as the query contains the primary key. And there is also a lot of polish that SSMS just doesn't have. Like how it forgets the order of your tabs as soon as they overflow. Or how you can't just do an ad-hoc query and see the result, you need to open a new query "document". >> NuGet constantly fails silently when trying to restore packages. > what? That was my reaction too. Sometimes it decides that it won't build at all because it complains about unresolved references. Sometimes it builds but assets will be missing. And of course it's an opaque black box in the usual MS fashion, so there is no way to force it to retry, or to find out why it's not cooperating.
- fhery 7y ago
  What about copying data between databases? I couldnt get it right in pg, meanwhile works fine in SQL Server Also pgAdmin has no(?) Intellisense.
  - Nullabillity 7y ago
    > What about copying data between databases? I couldnt get it right in pg, meanwhile works fine in SQL Server Export to SQL with pg_dump[0], or export to CSV with COPY[1] or \copy[2]. > Also pgAdmin has no(?) Intellisense. Press ctrl+space for auto-complete. It also seems to pop up when you press `.` (in a valid place). psql follows the more typical convention of auto-completing on tab. [0]: https://www.postgresql.org/docs/12/app-pgdump.html https://www.postgresql.org/docs/12/app-pgdump.html [1]: https://www.postgresql.org/docs/current/sql-copy.html https://www.postgresql.org/docs/current/sql-copy.html [2]: https://www.postgresql.org/docs/current/app-psql.html#APP-PSQL-META-COMMANDS-COPY https://www.postgresql.org/docs/current/app-psql.html#APP-PS...

by fhery 7y ago

juststeve 7y ago

When you type Install-Package in Visual Studio, sometimes it just fails to find the package at all. You have to search for it first, then type Install-Package, and then it actually downloads etc.

fhery 7y ago
I'm always doing it via Nuget Package Manager and I don't remember having any troubles with that I'm using dotnet's CLI mostly for migrations/publishing
- juststeve 7y ago
  Yeah i think package manager GUI is ok? but cli and powershell, not so much

Nullabillity 7y ago

> Wow, you must've been trying hard to cherry pick those. Not really. Just try keeping a .NET/MSSQL environment running for a few days, and the stories will build up quickly. > SSMS is mature, reliable and makes my life easier meanwhile pgAdmin is just viable, but nothing more. But psql is good enough that I pretty much never have to touch pgAdmin. And for ad-hoc editing (the only case where graphical editors have any real advantage), surprise, SSMS can't edit the results of custom queries. pgAdmin doesn't care, as long as the query contains the primary key. And there is also a lot of polish that SSMS just doesn't have. Like how it forgets the order of your tabs as soon as they overflow. Or how you can't just do an ad-hoc query and see the result, you need to open a new query "document". >> NuGet constantly fails silently when trying to restore packages. > what? That was my reaction too. Sometimes it decides that it won't build at all because it complains about unresolved references. Sometimes it builds but assets will be missing. And of course it's an opaque black box in the usual MS fashion, so there is no way to force it to retry, or to find out why it's not cooperating.

fhery 7y ago
What about copying data between databases? I couldnt get it right in pg, meanwhile works fine in SQL Server Also pgAdmin has no(?) Intellisense.
- Nullabillity 7y ago
  > What about copying data between databases? I couldnt get it right in pg, meanwhile works fine in SQL Server Export to SQL with pg_dump[0], or export to CSV with COPY[1] or \copy[2]. > Also pgAdmin has no(?) Intellisense. Press ctrl+space for auto-complete. It also seems to pop up when you press `.` (in a valid place). psql follows the more typical convention of auto-completing on tab. [0]: https://www.postgresql.org/docs/12/app-pgdump.html https://www.postgresql.org/docs/12/app-pgdump.html [1]: https://www.postgresql.org/docs/current/sql-copy.html https://www.postgresql.org/docs/current/sql-copy.html [2]: https://www.postgresql.org/docs/current/app-psql.html#APP-PSQL-META-COMMANDS-COPY https://www.postgresql.org/docs/current/app-psql.html#APP-PS...