> What feature do you need that isn't in the open source version?
ODBC support, Cassandra, Redis, and Azure (Table) Storage support, and support for the kinds of obsolete RDBMS and "4GL" you see in large enterprise and small mom-and-pop backrooms (Progress, Clipper, AdvantageDB, ElevateDB, etc). And SQL script debugging for Postgres.
Currently I have separate tools/clients/IDEs for all the different data systems I target (e.g. SSMS, MySQL Workbench, Azure Storage Explorer, Azure Data Studio, Excel PowerQuery, LinqPad for .NET Framework 4.x for both x86 and x64 because ODBC and OLE-DB are like that); while I have a modest set of portable-ish VM images of obsolete Windows OS instances where I can run MS Access 2003 or some Clipper derivative. I'm also still running Firebird and even FoxPro 9 in another VM somewhere.
...so yes, having a single tool which handles 85% of my tasks without needing to juggle VMs and multiple bloated Electron apps together would be an improvement for me and worth me paying money for.
> Why not fork it and implement that feature, and then use that?
"Fork it" is not a reasonable suggestion considering the amount of work involved (see above).
> If you don't want to deal with a company trying to extract profit from you, use the open source version. That's the way to ensure your own freedom
As I said, I'm perfectly fine with me throwing money at DBeaver. I'm just expressing my frustration with DBeaver that I think they're being callous by not offering perpetual offline licenses for Dbeaver Pro, for any amount of money. The fact they used to[1] but don't anymore suggests they were getting disappointing return business from deep-pocketed "enterprise" customers, but I'm disappointed that their solution to this problem of theirs means leaving my money on the table because now they don't have any product licenses that I can work with.
Your reasons are valid and make complete sense to me. I wonder if you could write to them and explain your use case and offer to pay for a perpetual license? No idea if it'll work, but worth a shot maybe?
If you try this, do update and let us know what they say.
ODBC support, Cassandra, Redis, and Azure (Table) Storage support, and support for the kinds of obsolete RDBMS and "4GL" you see in large enterprise and small mom-and-pop backrooms (Progress, Clipper, AdvantageDB, ElevateDB, etc). And SQL script debugging for Postgres.
Currently I have separate tools/clients/IDEs for all the different data systems I target (e.g. SSMS, MySQL Workbench, Azure Storage Explorer, Azure Data Studio, Excel PowerQuery, LinqPad for .NET Framework 4.x for both x86 and x64 because ODBC and OLE-DB are like that); while I have a modest set of portable-ish VM images of obsolete Windows OS instances where I can run MS Access 2003 or some Clipper derivative. I'm also still running Firebird and even FoxPro 9 in another VM somewhere.
...so yes, having a single tool which handles 85% of my tasks without needing to juggle VMs and multiple bloated Electron apps together would be an improvement for me and worth me paying money for.
> Why not fork it and implement that feature, and then use that?
"Fork it" is not a reasonable suggestion considering the amount of work involved (see above).
> If you don't want to deal with a company trying to extract profit from you, use the open source version. That's the way to ensure your own freedom
As I said, I'm perfectly fine with me throwing money at DBeaver. I'm just expressing my frustration with DBeaver that I think they're being callous by not offering perpetual offline licenses for Dbeaver Pro, for any amount of money. The fact they used to[1] but don't anymore suggests they were getting disappointing return business from deep-pocketed "enterprise" customers, but I'm disappointed that their solution to this problem of theirs means leaving my money on the table because now they don't have any product licenses that I can work with.
[1] According to https://dbeaver.com/docs/dbeaver/Differences-between-license... - they stopped doing perpetual licenses after v23.3).