It uses jdbc drivers for database support, so it can handle basically anything.
If one of the obstacles to data entry is normalization, perhaps an updatable view if your database supports it.
Not as common as you might think. It is a hard thing to search for, and the ones I have been able to find all suck.
I wrote a PHP application a long time that allowed you to create a GUI for an 'arbitrary' SQL database table, using an XML schema to configure the appearance, validation etc. of the fields. Life got in the way, and I stopped development before it was ready for prime time. Fifteen years later, I went looking for something with similar functionality and was surprised at how few options there still were.
I understand that a spreadsheet "row" often isn't going to be a normalized SQL table row and all that, but isn't mapping the spreadsheet cell ranges into such a schema technically the only problem here?
If you had a script that watches your spreadsheet for changes and can drop you into a SQL shell whenever you want, you'd have it both ways.
But the topic here is about GUIs which serve the middle-ground between the "scalable, real, full-blown database" applications and the lowly spreadsheet. The SQLite project offers nothing that is comparable to Access.
We can have our cake and eat it too.
The mistake with Access was that instead of keeping a deathgrip on its legacy file-based roots, it ought to have "grown up" and become a web-native HTML5 app that uses SQL Server back-ends as the only option.
I still think there's a huge market for something like this.
It is still available even in the 365 package but I can't remember when I used it last time. It was long time ago.
DBeaver fills that need for me.
There is an "in between" focused on structured data entry using forms (rather than tables), which used to be Microsoft Access (and Claris FileMaker), but these days is the realm of Airtable and Google Tables. But that's not ad hoc or random, you still have to build your forms and specify your validation rules and all. And they're more just about storing and retrieving records for small organizations, they don't support SQL directly.
Or, alternately, separate the config process from the install process. I'd be much more comfortable running config commands from a script inside the docker container, or as a first-run setup UI, or as a simple .yaml config.
It does look like something I'd like to try out later, though. Either after the install process is cleaned up a bit, or once I have time to read through the whole install.sh script.
Edit: In case it matters, my personal preference is to install things as linux packages instead of Docker, but I understand that this is a stretch for early-access software.
Our current installation process was spun out of our local development setup, which isn't ideal.
Cleaning up installation is one of the top things on our to do list. This also includes documentation for setting up Mathesar without Docker. We'd like to do Linux packages as soon as we can too.
The tool that was great for this is FoxPro.
Is like access, but the genius thing is that it include a super-charged "repl" aka: the command window.
It allow to combine GUI + Help + Terminal in one single tool, so you can do
use table
browse // show a data table
go first // you can navigate both by mouse/keyboard and by code!
But the theory is, I love the relational database, they are a sort of rigorous superset of the spreadsheet, and I have replaced all my spreadsheets with database tables, however while it is very hard to beat sql for rich comprehensive data transforms and analysis, ad-hoc data entry is very awkward. Most gui tools are focused on database administration and I want one for quick random edits. any hints?