Home » excel » sql – Humane PostgreSQL interface for non-technical people?

sql – Humane PostgreSQL interface for non-technical people?

Posted by: admin April 23, 2020 Leave a comment


I currently have lots of semi-static structured data in a bunch of excel sheets which I’m using on a website. The data changes very rarely, so I essentially load the data (mostly things like copy-text, translations, etc.) directly from excel using Apache POI into memory when I need it. It works great.

However, eventually I’d like to swap over to a proper database, ideally the same PostgreSQL database I’m using for the truly dynamic stuff. However, the advantage of Excel is that all the non-technical people I’m working with can directly edit it and have the changes show up on the website. I’m personally using pgAdmin to manage the DB as a system, but it’s too close to the machine for me to trust non-technical people with it.

Is there any generic CRUD admin interface for PostgreSQL that non-technical people can understand? Something like Django’s admin interface, exposing the bare minimum of CRUD operations in a easy to use way, without exposing any dangerous knobs or buttons, but not tied to any specific web framework?

How to&Answers:

You should probably look at pgAdmin. While it includes a lot of advanced capabilities geared toward software developers and DBAs, it has the Edit Grid tool, which sounds pretty much exactly like what you’re asking for.


How quickly do you need to get the data into the database?

I have this problem all the time. Typically, I solve it in one of the following ways:

(1) Have the users change the Excel spreadsheets and then have them automatically loaded at night. The data will be available the next day.

(2) Embed something in Excel to allow users to load the data directly into the database. The data gets loaded automatically. This could also be done by have an auto-close macro ni VBA.

(3) Rarely, build an application that loads the data into the spreadsheet and then let’s the user modify the data and write it back.

There is not enough information to figure out the best approach. However, keeping the users in Excel is a good idea, since they are most comfortable with that environment.