- Most clients are Java, which is a pain b/c
- they require you to list the DB in the connection
- JDBC drivers can not use a socket connection
- UI isn’t great
- Valentina Studio
- Has free & pro ($199) versions
- Was the easiest to get connected initially, but then found bug that showed it wasn’t using socket connection as expected.
- Linux version is a Wine app
- RazorSQL ($100 / year)
- Is a Java app
- Not much different from SQL Workbench, just use that instead?
- Electron, AppImage
- Wanted me to enter an email address just to use the software, became privacy concerned about how much stuff would get sent to their servers
- DbVisualizer ($197, $69 renewal)
- Downloaded & tried it, typical java app
- SQL Workbench/J (OSS)
- web based but still Java?
- too crude
- JetBrains DataGrip ($199 / $159)
- has lots of errors when used with PostgreSQL 11
- installed, couldn’t get past the splash screen which said it couldn’t find the application server
- Couldn’t get a DB connection to save
- Windows only
- No longer developed
- Windows only
- OSS and enterprise version
The vast coverage of JDBC is probably a good reason so many tools use Java. I'm sure you wouldn't prefer they all used ODBC or DBI instead.
DataGrip is fantastic and not expensive if you use other JetBrains products. It also manages its own JDBC drivers -- you don't need to install at the OS level.
Won't show more than a white screen because of "[Oracle] NJS-045: cannot load the oracledb add-on binary for Node.js 8.2.1 (linux, x64)" - this does not inspire confidence.
Website says "PostgreSQL, MySQL, BigQuery, SQL Server, Redshift, Snowflake, SQLite, Presto, Cassandra, Oracle, ODBC, and more on the way."
That was my experience as well. pgAdmin 4 is such a shit show.
As someone that has done lots of Java development you have lost me there, as JDBC drivers obviously do make use of network connections, usually TCP/IP sockets.
- Valentina Studio: support confirmed and fixed the bug in about a day. Waiting for the next release. Not crazy about some of their UI, but hopeful this will be my answer.
- DBeaver: going to give it a try
Well integrated ER diagrams that let you quickly see parts of the db related to current table, or the whole thing if you want.
SQL generation from structure or data edits. Great for cranking out DB migrations like a boss.
Ability to maintain many database connections at once, and support for doing stuff before/after connecting which we widely abuse to setup SSH and VPN connections.
Very liberal database support. My original search for a tool like DBeaver was from the need to connect to MySQL, Postgres, and SQL Server and not wanting to use a bunch of different tools. DBeaver supports roughly anything Java supports, which is everything.
Wide OS support. Good luck finding another tool that can connect to MS SQL Server on MacOs that isn't garbage or money.
The icon is also adorable
The only downside is a bit of classic FOSS UI clunk. Not nearly as rediculous as Eclipse or Blender or the like, but it takes a few days to get comfortable.
- Again I wonder why it doesn't show the tables first, I have to go through Schemas -> Public.
- 480 MB of RES RAM, I'm connected to one smallish Postgres DB.
- I can't even find "just show me the contents of the table, like 'SELECT * FROM'.
I know, maybe it's tailored for Enterprise Database Architects, but this is my smoke test for a DB GUIs:
"How long and how many clicks does it take so that it provides more value than: 'psql; \dt+; SELECT * FROM X;'"
Mouse over the buttons for an excessive amount of time and the tooltips will tell ya what they do.
Double click a table and go to "data" tab to see contents.
Schemas ->public is just a side effect of supporting a lot of different databases. Many support schemas
Ram is because default java heap size, you could probably change launch params to get it much lower though.
On all counts other DB tools I've used are just as obtuse and burn tons of resources. Most are written in Java or another high-level language because it's nigh impossible to get DB drivers for a ton of different databases working together in C. DBeaver is basically leveraging JDBC for what it was designed for
And yeah, I found "data" and maybe reading the manual would even let me somehow get there quicker. Still, I don't remember ever working with Postgres (or Oracle) in whatever role or project and not needing the "data" view 10 times as often as the schemas or other stuff :)
Closest thing that works for me is TablePlus but the UI smoothness is still rough around the edges.
These guys actually fix their bugs. It works on every database known to humans, and also does nearly everything DBeaver appears to do.
For many people, including me perhaps, something like DBeaver is good enough since it's free.
Compared to a six-figure salary? Developers tools are a bargain for what we get out of them.
I've been shelling out for IntelliJ Ultimate for years because I want to support JetBrains. At this point I think I could actually get away with just the open source Community Edition, but it's worth paying them for the effort in my mind.
I don't mind buying good software, but it feels weird for me to pay in order to make my employer more money. It's not like the productivity boost I get from buying Datagrip is going to get me a raise or a better job.
That said, for software I use in my personal life I can and do pay, and I think we should all be more in the habit of either buying non-trial versions (Sublime, PyCharm) or making small monthly donations (Neovim, iTerm, regex101, QMK, et al).
It’s not universal but definitely not uncommon.
If no part of your toolset is within your budget, then you're in the working class, since you cannot ever own your own means of production.
You only transition once your investment returns surpass your income. Which is why truly rich people don't give a shit about income tax - they don't have income!
For example, in the UK, commonly doctors and lawyers have not been considered part of the working class, regardless of if their investments outside of their profession.
Because a doctor can work independently, and hire other workers like nurses, and attendants, and own all of their tools of trade outright, they are part of the petit bourgeois.
Now you say that petit bourgeois is part of the working class, but many would disagree as Karl Marx and Friedrich Engels popularized a more fine grained definition of social classes as follows:
1. the working class - factory workers, peasants, and people who earn only by their labour
2. lumpenproletariat (commonly considered to include vagabonds, criminals or the 'unthinking poor')
3. professional middle-classes (engineers or tradesmen who do not typically hire employees)
3. petit-bourgeoisie - Professionals and small scale managers who hire workers but work alongside them
4. haute bourgeoisie - landed aristocracy & other capitalists who live from investment alone
Now if you are not marxists, you may drop some of the classes or simply call them something else. The lumpenproletariat are sometimes called the "underclass", and in advanced capitalist economies the line between professional middle-classes and petit-bourgeois blurs due to capital infusions from the top. For example, startup owners should rightly be professional middle class, but are upgraded due to VC infusion.
There are other ways to define the classes as well that don't depend on monetary wealth----for example the ladder from: working class to bourgeoisies to gentry to elite/aristocrats, so the terms themselves are fairly overloaded.
Analysing class warfare is a bit of my hobby. I blame my sassy liberal arts professors. :)
I can't speak broadly, but when I worked construction, most guys would bring a mix of personal tools and company tools.
I don't understand why you don't to become a more productive person then you may get a better job offer or start your own company where you and your customers will be the one to evaluate your worth instead of a single boss of yours.
Then remove 25% as social charges + ~1 month of net salary as income tax + other various types of taxes.
That said, I have a JetBrains subscription because their suite has a lot of value if you deal with multiple types of databases (or Java/.Net). Their business model is refreshingly straightforward, the coding is solid and I don’t mind giving them money.
But you're probably right.
Also good tools are worth paying for, I have been a subscription user of their tools now for years.
I think it's like $199 for a subscription to the whole suite. If you are a dev (or work for someone who expects you to do dev work for pay) it's worthy spending a few of your coins on good tools.
I stare at these tools all darn day, and they rarely if ever crash. I don't regret moving away from Eclipse almost a decade ago, which used to devour all my system resources and crash and fail constantly.
When saying something is not expensive (few of your coins), consider that it might be just your situation where it's not expensive.
What is the paid version of grep/ripgrep that works better?
Not ALL tools need to be paid for.
If I say I'll do some work for free the we can assume you don't need to pay for it.
I use IntelliJ, AppCode and that already means I should be using all products pack which I'm subscribed to.
But the real power of DataGrip comes by using it in one of their IDE that auto completes table and column names inside code and allows you to shift-click it to get to see the definition and show warning when you specify an unknown field.
There is absolutely no reason DataGrip needs to be a subscription service. There aren't any ongoing costs for customers to use it.
It should be a one-off purchase with optional support subscription, maybe requiring re-purchase at major version increments, not this bullshit where you need to maintain a subscription for a license on a binary program you already paid for and installed.
Feels as dodgy as Adobe turning Photoshop into a subscription service
Fuck these business models and the sales idiots who try to apply them to every single product
First, you have to define the difference between "major" and "minor" version. Users expect major versions to have some significant improvements or new features. What this means is as a developer, you have incentive not to release minor features regularly, but instead batch them together so you can do a "major" release.
Second, the sales team now dictates the release cycle. More major releases means more money, but do it too frequently and the user base revolts. In many companies sales dictates the releases, but now if development is late it's messing with the company's cash flow and ability to continue to exist.
Third, the software can never be "done", because that means no more major releases. As a result, unless there is a sustainable stream of new users, you get feature and scope creep.
Subscriptions mean predictable revenue, and make the developer's incentive align with users: keeping users happy. This means keeping the product stable, making incremental improvements, and evolving with features that make sense.
Of course the beauty of the market is you should be able to find products sold both ways, and you can choose.
I've bought Mailplane v3 for my Mac a few years back. The app did not get new features, only patches. New features came out with v4, which required another purchase. I didn't buy it because v3 is good enough, buying again is a psychological wall. If it was a subscription I'd be happily paying them and happily using the latest version.
They are not charging a subscription for you to be allowed to download Gitlab and self-host it.
The issue with a subscription for self-hosted or locally ran software is that you are obligated to pay an ongoing fee, without the provider being obligated to provide any service in return. Their terms do not require them to adhere to any release schedule or anything showing that by paying a subscription you're getting X. It's basically a recurring donation in hopes the software you already paid for gets an update.
Imagine if your OS required a subscription for your computer to be usable, even when the developer of your OS doesn't release any updates that benefit or affect you for months, if you don't keep paying your subscription you get locked out of all of your work for no reason other than some marketing douche thought it'd be a good way to squeeze a more regular revenue stream out of their existing customers?
You can see it on the “buy” page.
It’s still less than ideal, but I pay yearly for their “all pack” product and I feel with the amount I use it I’ve gotten my money’s worth every year.
Not sure if they changed this recently - I stopped following them when they switched to subscription with fairly onerous terms (which they rectified after backlash to ‘mediocre’, but never to ‘fair value’).
The reason this is more fair is that I am paying for the version and one year of updates. Jetbrains has no right to say at the end of the period that since I did not renew, they are taking back the updates they gave me, as if it was by their grace I had been given the updates. I paid for the updates, I get to keep them.
That said, they have every contractual right to enforce whatever they think is fair, and I have every right to recommend against their products and/or prevent the bulk purchase if I am in a decision-making position about it.
In order to keep using it, I would be required to downgrade to the version available at the beginning of my subscription. 12 months ago.
If there are show stopping bugs in that version, then too bad. If it's not compatible with your current projects and plugins? Deal with it.
With most software, this would not really be a huge deal. Photoshop? Who cares. Excel? Meh.
But with Jetbrains products you've got to consider whether the old version is going to be 100% compatible with your existing project files, plugins, keybindings, settings and configurations.
It's quite a gamble IMHO.
If you want major updates, it's not weird to be asked to pay for it, which means continued subscription.
The issue with a subscription for self-hosted or locally ran software is that you are obligated to pay an ongoing fee, without the provider being obligated to provide the service you're paying for. Their terms do not require them to adhere to any release schedule or anything showing that by paying a subscription you're getting X. It's basically a recurring donation in hopes the software you paid for gets an update.
If they quit updating to abandon (which is unlikely when they're making quite a ton from the subscriptions), you can quit paying.
It works on every database known to humans
We're fully on Jetbrains tools otherwise (R#, dotTrace and dotMemory, TeamCity as build server) so it was a no brainer for me to want to continue that trend but it didn't check all the boxes for us, despite its clear polish.
I tend to hate any IDE built on Eclipse (which I think DBeaver is), but I've been very pleasantly surprised with how well it works.
1. It's got very nice ER modeling where other tools (Like Oracle SQL Developer) make you jump through a dozen screens and a wizard to make a simple diagram.
2. It's got nice export tools to get your data to business partners in a more convenient way. Sure you can copy tables in pretty much every tool but there's just an 'excel' button that can pop open your current query in a new sheet.
3. It does have a weird delay when opening up databases sometimes where it 'reads metadata' about the table and it can sometimes take a long time to return even the most basic query. But once it's cached that data I've not noticed problems after that.
4. It does seem like the document database tooling isn't as baked as the relation tooling. I routinely get hangs when querying my Mongo collections, which is sometimes a drag. But it hasn't been a huge issue.
Overall, I'd highly recommend the paid version of this tool as it's helped me consolidate: Robo3T, Sql Server Mgmt Studio, SQL Developer, and MySQL Workbench into a single tool.
My previous workplace used to be locked into the Microsoft ecosystem and the core legacy product was backed onto a Microsoft SQL Server DB.
Over the years we pushed the business to move away from the MS/Windows ecosystem. When this happened, like many others, I looked for a UNIX compatible DB client that supported SQL Server.
First, I tried SQuirreL and it was horrible. I just had to uninstall it and keep looking. I settled on DBeaver for a while as it has some nice features and it did most of the things I needed it to, but it was not particularly polished.
Eventually the business decided to pay for Jetbrain's All Products package which includes DataGrip and from my experience you could say: Eclipse is to IntelliJ IDEA what DBeaver is to DataGrip.
The other product I was looking closely at was Navicat for SQL Server, which looks pretty damn good and those who use it seem to swear by it. However, I am not a DBA and for that reason I can't justify the USD$699 personal licence price tag of Navicat.
DataGrip is not perfect, but it's pretty damn close and I think its price tag is well justified.
The embedded DataGrip can be a good tool inside one of their IDE though.
Except any non-relational DBs.
MySQL, Postgres, SQLite, etc...all the tools I need in one app.
I generally try to avoid Eclipse-based projects because they can be very bloated, but in this case it's easily justifiable.
So DBeaver scratches my itch of needing same tool across platforms, across databases.
Try binding MySQL to 0.0.0.0 (all interfaces) instead of 127.0.0.1 (loopback). That said, 127.0.0.1 should be fine provided you connect through the service name or the docker container IP), connecting via 127.0.0.1 doesn't make sense. Then again, it's docker on Mac, so I don't really know.
Fwiw, also used sequel pro on Mac, moving to Linux dbeaver was the only thing that came close.
Now I don't really mind either but dbeaver is a bit quirky overall.
Being told about Dbeaver and reminded of pgModeler right now is great because I am currently defining the tables for a project I am working on for a client, and as the number of tables grow jumping back and forth between the files that define each of them adds a still small but noticeable overhead. With a ER diagram tool I might be able to speed up a little part of the definition work.
Edit: Hmm, pgModeler might still not be such a great tool https://news.ycombinator.com/item?id=17693582
It's shocking to me, actually, how absolutely awful most SQL clients are. It truly was an area that was ripe for "disruption".
Used HeidiSQl for a long time but got fed up with issues with it freezing or crashing, especially when switching DB connections.
Dbeaver has been fantastic! Has some feautures Heidi didn't have, very stable & better looking UI. Thumbs up from me, definitely worth giving a try!
HeidiSQL feels like a finished product to me. Really no complaints at all and if you actually take a look at the commits, you'll see that the SINGLE developer puts in a whole lot of effort.
The guy is great and calling the project abandoned is really not fair.
I'm not sure if it is just an issue with my machine, because others in my office still use Heidi and don't report the bugs I am having. Small as they are, they got annoying enough for me to start seeking alternatives. I would still recommend people giving Heidi a spin if they've never tried it.
HeidiSQL (with WINE) is still by far the best SQL client for me, because the UI is simple yet efficient and very clean.
A whole lot of my work ends up with a three- or four-column table with one column of buckets, and the other being counts of how many things ended up in that bucket. I'd love a view where I could render that into a line or bar chart as a sanity check, and have it update in real-time as I change my query. Instead, I end up having to constantly copy/paste into Excel and do it there.
Yes, I should be using a proper BI or visualization tool for real reports. But sometimes I just need a quick line chart to show that yes, that one count is going in the right direction.
DbVisualizer also has built in charts that are simple but... not free/open source.
It's not perfect but it's not bad. My experience was annoying (at best) to get drivers to work; particular the tsql ones (since Microsoft didn't provide Linux drivers at the time -- I don't know if that's been rectified). Once they're working though, everything else is fairly intuitive.
It's been a couple years since I moved to a different team and no longer need to connect to databases (and can't anymore... yay security). But I've considered using DBeaver at home for personal use.
Aesthetically, it looks great though. I wanted to like it.
Postico is very similar to Sequel Pro, simple but effective.
Navicat is the more feature complete option, but using wine on Linux is not cool.
I’m very happy with dbeaver.
Long time ago I started searching for a DB-client similar to "TOAD", but on Linux and targeting only my following key requirements: 1) write & execute single SQLs on a "page" which has multiple SQLs without having to use any terminator (";") between them, 2) ability to show the execution plan of the SQL in which the cursor is positioned and 3) ability to connect to different kinds of databases.
I ended up with nothing, and I actually even initially excluded DBeaver as running on Java (personal thing - most Java apps I tried always had some kind of bug which made it a no-go for me).
After a while I gave it a try and I ended up being extremely happy with it, especially because I can use it with basically all databases that I am/was using (I'm currently using it mostly with MariaDB & Clickhouse, but used it in the past as well with DB2, Kudu, PostgreSQL).
Inexpensive and light weight.
I just discovered DBeaver today, and while it's not up to the standards of SSMS (which is an amazing tool) with SQL Prompt, it so far beating the pants off Navicat.
I’ve been using DBeaver and I’ve been very happy with it though. Paid for the enterprise license to help support it too.
The biggest tools from Navicat that I miss within DBeaver are the data sync and schema sync tools.
If you like a cli tool, http://henplus.sourceforge.net/ is ok and easy to modify if you feel inclined.
It's written in Jython and used jdbc.
There is a version with line-editing around using jline.
There are so many free tools for databases and I'm wondering : How do the devs survive with free versions and/or open source?
Don't think donations will amount to any relevant amount.
Plus, the built-in support of SSH tunnels is a big plus for my use cases!
I use Dbeaver regularly and am very happy with it.
And why the hate for Java? Most other languages have runtime libraries or VMs too, does it really make a difference if that runtime code is baked into the exe vs. stored in a separate folder?
(I tend to be the opposite - if I can find a Java based tool to do the job I'll choose that because they tend to be very self contained, don't often require messing around with other OS dependencies ...)
Fortunately there are good ways to get it. OpenJDK and Azul have much more hassle free installations now. I personally use sdkman , but conda  is another very easy way to get java that won't hassle you.
Not that I'm trying to persuade you or anything - I was just curious!
Gave my honest thoughts on this and lost 3 karma points. Not too bad this time. I still have a few more to spend.
I'm mainly interested because I write a lot of software that needs the JVM to run (I don't use Java itself much, but it comes to the same thing). So it is very useful for me to understand reasons people would reject my software.
- Bob unzip a Python package.
- Dennis suggested we hire a "penetration tester".
- Mrs. Fraulein was caught browsing "Jew Tube".
- Helen used an essential software product from a "Pentaho"company for more than three years. Mr. Flanders was so disturbed he bought that company and renamed it "Itachi Vantara".
- Raul was using "Zope" to build our Intranet, until our Purity squad learned it was an insult in Spanish.
- David boasted about installing "OpenSIS" at his university.
- Susan was reported for surreptitous use of "ClamAV".
I also recommend terminating Derek for using "Google". It's not in the blacklist, but it just sounds obscene.
It's a particularly lowbrow bit of slang and not something that worried me when I recently mentioned the name dbeaver in a professional context, although I am aware of it. It pleases me that I spend my time among people that are either ignorant of this matter or are happy to pretend they are.
I guess a followup question for those who've been talking about this tool with colleagues, do you just casually call it "beaver" or the full "dee-beaver"? I want to call it "dee-bee beaver" but there's a missing b...