Port DBA module to 7.x

Not until the 5.x version works enough for a 5.x-1.0 release, I'd guess.
See #138877: Can't backup database from table list among others.

Sorry, wrong status...

If it were me, I'd say the D6 port shouldn't start until the following are all fixed:
#138877: Can't backup database from table list
#103911: Failure of automatic backup with large database
#103906: Mailed database backups have mal-formed attachments
#132810: dba_run_script() truncates lines to 8192 bytes

and perhaps this, too:
#45769: Serious translations problems

subscribing.

subscribing

Subscribing.

Subscribing. Port to 6.x would be nice, though it is a good idea to port a stable version, certainly

Subscribing.

+1 subscribing

+1 subscribing

+1 subscribing

I see this issue was opened in June 2008.
Is the developer still actively supporting this module, as it does not look he is replying here?

I nor any of the other maintainers have been able to actively support this module for some time. I keep expecting to have time "soon", but "soon" never seems to be "today".

I know the feeling ;)
Hope you can get around to it soon.

+1 subscribing
1. Any one has made any port and cross checked for Form API 2.0?
2. I saw a list of vulnerabilities for 5.x-1.x-dev version?
3. I am trying to give a shot at porting any suggestion and help is welcome

6 would be good. This is an awesome module.

It's important that the issues in #3 be addressed as you don't want to port the problems, too. Issue http://drupal.org/node/103911 seems particularly critical in my case. I've had decent success following the solution I reference in my post on that. If you go to a file based system, most of the problem is resolved but large tables still cause memory issues. http://drupal.org/node/103906 also has a possible patch posted.

@New Oceans: It's confusing if you keep editing your existing comment, and the people subscribed via email never see your "updates". If you have something new to add, put it in a new comment. Thanks. ;)

@dww: Here you go

Definitely prefer to access the database via Drupal.

However, as long as there's no 5.0/6.0 version I'll stick with sqlyog*:
- http://www.webyog.com/en/screenshots_sqlyog.php

Another tool (webbased) which might be worth looking at - for the time being:
- http://www.sqlbuddy.com/screenshots

And A complete list can be found here:
- http://www.smashingmagazine.com/2009/03/25/mysql-admin-and-development-t...

* NOTE
Needs remote access - ask provider

I just wanted dba for D6 for some basic stuff (viewing, updating, describing tables,etc. I don't have access to other tools), so I tried to port the module. The basic stuff is working now, but not fully tested.
Anyone interested in the code? I'm fairly new to Drupal.org; I don't know if it's regular or allowed to just dump a zip-file here.

Erik Greve
www.kennisakker.nl

@henkiejan: Thanks. Generally, a .zip file of a bunch of changed files is not helpful. If you can create a patch, it's much more likely that some of your work could be useful to others.

Thanks,
-Derek

@henkiejan: if you will contact me thru my contact page here and send me your files, I will try to make a patch suitable for raw testing. It should be a good exercise for me and might help move things along here.

Just to let know I'd love to see a D6 version: subscribing ;)

@henkiejan: offer still stands. Will send you a note via contact page if possible.

+1 subscribing. a dba module for 6.0 would be fantastic

Does this module need to be assigned to Abandoned Projects?

Pretty close, I'd say. It's originally Jeremy's baby. He never fully let go of it for me to do with as I please, so I don't feel comfortable answering on his behalf. I certainly don't have much time for this module anymore, and a responsible co-maintainer would be lovely... that said, this is an especially dangerous module, and the security implications are nasty. So, if someone were to take over, they'd really have to be well-versed on security issues.

Anyway, what do you say, Jeremy? ;)

Jeremy's last commit was over 2 years ago. Looks abandoned to me?

I plan to rewrite the module from scratch for Drupal 7, actually. I have a need.

The port to 7.x is underway. At this time the only thing that somewhat works are manual backups of one or more tables. Over time hopefully the module will gain back all of its previous functionality, however my initial interests are:

• Adding support for working with any database configured in settings.php
• Whenever using the Schema API is not sufficient, provide functionality in a pluggable way that degrades gracefully (allowing plug-in support for different database types)
• Being able to view/edit all information about tables and data in tables, for any database type
• Using AHAH to dynamically show/hide enable/disable buttons based on what is currently possible (for the current database and/or selected tables)

Better title for when this shows up in my tracker page. ;) Also, looks like Jeremy's working on this, so I'm assigning it to him.

There are currently two reasonably working features that could use testing:

• Viewing one or more tables: the 7.x-1.x-dev version of the dba module allows you to view the contents of multiple tables at a time, paging through each table independently. It is also possible to control which columns are displayed within each table.
• Exporting tables: the 7.x-1.x-dev backup functionality has been renamed to "export", and exporting to the following formats is currently implemented: CSV, HTML, mysqldump, OpenOffice Spreadsheet, OpenOffice Document, Microsoft Excel, and Microsoft Word.

The next major feature added was annotated mysqlreport output for MySQL databases, and very limited annotated report output for PostgreSQL database, detailed here. I'm going to go ahead and close this issue, and track progress on the main project page.

Keeping track of this thread...

So, despite the title, the original question was re: Drupal 6. Do the above latest comments (and the state of the project page) mean that there is not now/never will be a DRUPAL 6 DBA module?

Perhaps one of you has an alternate idea? I have a very stubborn and equally clueless client-user that is insisting he has read-only access, minimum, to EXACTLY and ONLY the LIVE db for the site. I'm on Pantheon, and I'm so not giving away my master password to this person. The DBA module was my only hope, at this point, because of the "two permissions: 'dba view database' and 'dba administer database'" capability, with 'dba view database' being the relevant need.

I've already suggested everything else, as helpfully and politely as possible - an rss feed giving him the fields he needs, a web service exposing what he needs, a manual dump and/or automated backup snapshot I-send-him/is-available-on a regular basis - every thing I or anyone else has been able to think of to shut him up (excuse me, I mean "serve his requirement"), and nothing I'm suggesting is working. For this guy, nothing is going to suffice but actual access. The best I can hope for is some way to give him read-only access so he can't take the site down while poking about. Is there another module besides the DBA module that can allow this to happen? Any other suggested methods with similar outcomes?

Any thoughts appreciated.

Thanks,
Kelly

@rkdesantos: I've sent you my code 3 years ago, but unfortunately not seen any patches.

I can't generate patches, so that's why I don't see any other way than to upload a zip-file with my code for D6.

Erik Greve.

Hi @henkiejan: Sorry I had all but given up following this issue. I've not made a patch myself in ages so I can't be of much help with that. If I ever received your files, I have no record of it.