There is ample PHP support, and even Python and the like (see the APSW suite by Roger Binns for instance). PHP of course supports also MSSQL and PostGres and the like, there is no need to be "stuck with MySQL".
As for phpMyAdmin - that's a different story - the strength of phpMyAdmin is of course its browser-based interface and how it integrates with the likes of CPanel - but there is a host of tools for all kinds of DBs with even better functionality (such as MySQL Workbench), though I don't know of one which does a similar browser interface - so for the rest you'd need a session access to the actual server. (Maybe someone else knows of such a tool for the other DBs). If you are happy to log in to the server, we could suggest a few great tools - but please note that there is nothing wrong with MySQL as far as web development goes. There is no need to change to SQLite, what is MySQL doing wrong? A major consideration is that MySQL offers user log-ins per DB (so you can give access to clients per project for instance). SQLite is awesome for local storage, but not every job requires such a hammer. On 2016/04/20 6:12 PM, Cecil Westerhof wrote: > I am blowing the horn for SQLite. ;-) A colleague of mine likes it in > principal, but he provides web hosting with a database. He has to provide > his clients with a web based interface for maintaining there database. > Because of this he thinks he is ?condemned? to MySQL. > Is this true, or would there be a plausible way to work with SQLite? >
