As a developer how much of a pain in the ass do you find it when you have to edit something in the database for the project your working on at that current moment in time, whether it be a CMS Module, some Core Modifications etc

Most of the time you end up having to have phpMyAdmin open anyway or something equivalent. But I'm reckon we should have something in the ACP(Admin Control Panel) that will allow us to work in a Single User Mode and on the CMS tables to modify them as necessary, create new ones, modify their internals etc

It should be fairly trivial for anyone with decent exp in PHP and MYSQL to replicate the functionality in a decent fashion, it should also remove the need for a separate application to manage the db the CMS resides in also.

Ofc this potential module does open up a few issues both security and stability wise, it could only take a small bug to cause irreversible damage to a content table or the user tables also it would need to run permission checks for the SQL user in use, so the GUI can accurately show functionality available

Comments, questions etc are all welcome

as a module, sure, but not as part of the core...

why not part of the core? don't forget it'll be behind the admin restrictions and it'll be restricted to the current working DB and possibly even the CMS tables only

Well no, we want the CMS to be lightweight and additons to be added after, else people will download a big hefty cms, where really, they want to easily customise it.

Not to mention most admins don't know what the fuck a database is or what they're doing with it.

My point exactly. Is it too much to CTRL+T, type the url and append the /phpmyadmin at the end and you're done ?

Use the CLI if you feel more comfortable then.

Infy most setup have to go thru a cpanel type setup to get to their PMA or equiv, if you install a LAMP Stack Manually you still have to install PMA if you wanna use it, i personally dont see any reason why the CMS shouldn't have its own version, even if it is a module.

Keeping in mind that the majority of the community atm are developers it'll be beneficial to us to have something thats useable in the ACP.
that may be so, but thats why we have the interface tools for em

I guess it's your CMS and you're going to do what you're going to do, I just feel like there's better things to focus your time on than your own version of phpMyAdmin (which will add a few MB to the project), that admins don't know how to use and will simply confuse them.

It's helpful only to a very select number of devs, and even then it's simply convenience. Admins of a CMS don't need to mess with the database at all. Every tool they need is part of "User management", "Forum management", etc. It is only good for developers of CS CMS. If you're an admin of a site, you should NEVER need to directly edit the database.

a few mb? tis a little OTT esp as I'm only proposing it have the abilities to edit the db the CMS resides in and possibly the CMS tables only.

As for it being 'convenience' to a degree i will agree with it, with there are situations where you have no tools available to you.

At the end of the day, everybody here has a valid point.

Linky is right in that moving around to get to PMA is a bitch sometimes, but In my opinion the pros don't outweigh the cons. Having an extra chunk of code as part of the default installation is OTT, As a module, great, shove it in the forum and wait for a community dev to create it. But not now...

I will also agree that having this module is just pure laziness. but hey.

And Before anybody bitches at me, Yes I've not touched the repository in a while, I've been shit busy with work, I'll up some code before the month is through.