Ticket #84 (closed enhancement: invalid)
Might As Well Add Database Services
| Reported by: | reachmike@… | Owned by: | juruen@… |
|---|---|---|---|
| Milestone: | Component: | web | |
| Severity: | minor | Keywords: | database postgresql mysql sqlite port access web pruning |
| Cc: |
Description
I noticed that PostgreSQL was used in the product. If you're going to do that, you might as well consider turning around and offering that as a feature service. And, if you're going to do that, you might as well load MySQL and SQLite as well.
Want my advice on the web interface? Well, think about the non-programmer, Linux-shy customer who wants to know that he can connect his MS Access to this (via linked tables) and know that now his team can share databases in a more robust fashion and have proper database backup, pruning, etc. So, from that perspective, and keeping things KIS (Keep It Simple), they may want to be able to start and stop the various database servers, and reschedule a good pruning time (one is scheduled by default automatically at 2am their time), and be able to create a new empty database or drop one. They may want logs that they can view, and if the pruning goes bad, be able to boot back to the last good database before the bad pruning time. They may want a simple web field that they can type SQL commands in and this can get passed in the background to 'psql' or the tools for MySQL and/or SQLite. If they want something more, then they should connect a tool to it remotely. These ports are going to need to be firewalled properly and available when one needs them.
(Sidenote: That brings up a topic about ports -- you may want all these services to have an option where default port numbers can be changed so that weakly-patched systems have less of a chance of getting hacked.)
