Port to 7.x
zmove - June 19, 2008 - 19:46
| Project: | Database Administration |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Hi,
Is there a plan to post this module to drupal 6 ?
thanks
zmove
#1
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.
#2
Sorry, wrong status...
#3
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
#4
subscribing.
#5
subscribing
#6
Subscribing.
#7
Subscribing. Port to 6.x would be nice, though it is a good idea to port a stable version, certainly
#8
Subscribing.
#9
+1 subscribing
#10
+1 subscribing
#11
+1 subscribing
#12
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?
#13
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".
#14
I know the feeling ;)
Hope you can get around to it soon.
#15
+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
#16
6 would be good. This is an awesome module.
#17
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.
#18
@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. ;)
#19
@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
#20
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
#21
@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
#22
@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.
#23
Just to let know I'd love to see a D6 version: subscribing ;)
#24
@henkiejan: offer still stands. Will send you a note via contact page if possible.
#25
+1 subscribing. a dba module for 6.0 would be fantastic
#26
Does this module need to be assigned to Abandoned Projects?
#27
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? ;)
#28
Jeremy's last commit was over 2 years ago. Looks abandoned to me?
#29
I plan to rewrite the module from scratch for Drupal 7, actually. I have a need.
#30
#31