MySQLDumper-Board Forum Index Follow me on Twitter

Portal  •   Forum  •  Downloads  •  Profile  •  Search   •  Register  •  Log in to check your private messages  •  Log in  •  


 MySQLDumper 1.24 stable released

Post new topicThis topic is locked: you cannot edit posts or make replies.
Author Message
DSB
Developer
Developer




Age: 45
Joined: 30 Apr 2004
Posts: 17273
Location: Herdecke


germany.gif

PostPosted: 2009-09-18, 15:56    MySQLDumper 1.24 stable released Reply with quoteBack to top

Dear MySQLDumper-User,

we just released MySQLDumper 1.24.
Download: https://sourceforge.net/projects/mysqldumper/

We also provide some additional services: http://www.mysqldumper.net/services/

Credits: http://www.mysqldumper.net/credits/

Changelog of the most important changes compared to version 1.22 (1.23 never left the beta status):

- MySQLDumper 1.24 still is working on PHP4 and PHP5
- new, light and friendly style. The "old" style is still included.
- better use of RAM
- backup and restore via PHP is about 25 percent faster
- possibility to select tables when doing an backup or restore
- use different configuration profiles to manage different MySQL-Server or -user.
This way you can maintain different MySQL-Server with a singel MySQLDumper-Installation.
- the internal SQL-Parser has been improved (more backups from other programms can be importet)
- SQLBrowser: a lot of bugfixes and some improvements (nevertheless it must still be regarded as experimental)
- SQLBrowser: a comfortable fulltext-search lets you find text even when you don't know in what column it can occur
After editing a record you get back to the hitlist. That really is comfortable when you need to change data.
- Tools: in version 1.22 the export of data as file didn't work. Now it is working again.
- the Web-GUI has been simplified. Some parameters have been removed. (You nearly have no chance to configure something incorrectly Smile )
- FTP-Transfer: address up to 3 ftp configurations simultaneously in one backup process
- Tables of type VIEW or MEMORY are now detected and data is not saved but the structure of the table is
- the directory work/structure is no longer needed
- the automatic "structure only" backup has been removed
- better and safer handling of encodings of backup files
- better and safer error-handling
- the backup converter has been rewritten. Now it also automatically converts big files into Multipart files.
- no notices in server-logs
- when adding SQL-Queries to the SQL-Library you can now enter more than one query. If using "commadn before/after backup"
these queries will be executed in a row. Succes or failure is written to the log file.
- When creating a password protection the password strength is visualized.

crodump.pl:
- when you can call crondump.pl in the standard directory "msd_cron" you no longer need to enter the
"$absolute_path_of_configdir" manually. An automatic detection was added.
- better and safer catching of errors
- logging of events is much more precise and gives you clear statements what happened
- automatic deletion now regards Multipart files as one complete backup and works the way you expect it to work
- automatic deletion is done after the backup process. In case of errors this retains your old backups you might need.
- the config parameter - which configuration profile is to be used - can be set in 3 ways. The missing suffix
".conf.php" will be added dynamically.
1. config=mysqldumper.conf.php
2. config=mysqdumper.conf
3. config=mysqldumper

- removed signalhandler:
When crondump.pl was started via a cronjob there was a malfunction. On some, rare server this signalhandler caused a second
or third instance of the script that never stopped and stuck in the process list. In this case the process must be killed manually.

... and many more small or big bugfixes and cleaning up the code

When you want to know more, just take a look at the changelog of my code changes at Sourceforge. Each change
of the code is documented here:

http://mysqldumper.svn.sourceforge.net/viewvc/mysqldumper/trunk/?view=log

Have fun using this version.

With best wishes from Germany,

your MySQLDumper-Team.


Last edited by DSB on 2011-01-18, 20:37; edited 1 time in total

OfflineView user's profileSend private messageSend e-mailVisit poster's website    
Anzeigen











Posted:    Anzeigen Back to top


    
DSB
Developer
Developer




Age: 45
Joined: 30 Apr 2004
Posts: 17273
Location: Herdecke


germany.gif

PostPosted: 2009-09-19, 13:03    (No subject) Reply with quoteBack to top

Roadmap to version 1.25

or what we want to do next.

We laid great stress on HTML validation following the rules of w3c (except the frameset definition to avoid margins) and tried to avoid any output of PHP notices no matter which PHP engine is running on the server. But although MySQLDumper is working fine on nearly any server and the core is really stable, we are aware of some things we need to change.

The code grew historically since its first release in 2003 and so did our skills. When you are a programmer and take a closer look at the code you will find lines where you'd like to say anything from "Ouch, what's that?" up to "Wow, brilliantly tricky!".

The greatest disadvantage at the moment is that there are hundreds of hardcoded echos in the code and that output is often generated by concatenating strings. Nowadays this is bad coding style and it makes it very hard to maintain the code or to find errors. We absolutely want to get rid of this. Wink

Our very next step is to strictly seperate the logic of the code from the layout using templates. We will fight all these echos down until there is no hardcoded output left. This process has already started and you will find some places in version 1.24 were we implemented template output. But as we still have a lot to do and it takes a lot of time to refactor the code, we didn't want to let you wait any longer for the next release. That is why version 1.24 came out with a mix of template and hardcoded output.

On our way to this goal we will detect last text outputs that are hardcoded and are not multilingual at this moment. Of course we will replace them with language variables to make them multilingual.

Additionally we will clean up the code. There are different functions that nearly do the same and which can be replaced by one function. To put it short: we will clean up the code and refactor a lot behind the scenes. If we do our job well you won't see anything of that in the gui. Wink

But after reaching this goal we are ready to enrich the web gui with some nice web2.0 functionalities. I don't want to get in details here now, but we do have a lot of ideas how to make the user experience even more comfortable.

So follow this project and stay excited. Smile

_________________
Gruß / Greetings, DSB

Teigwaren heißen Teigwaren, weil sie Teig waren.
Diejenigen, die lautstark darüber diskutieren, warum es nicht geht, mögen bitte jene nicht stören, die es gerade tun.

OfflineView user's profileSend private messageSend e-mailVisit poster's website    
DSB
Developer
Developer




Age: 45
Joined: 30 Apr 2004
Posts: 17273
Location: Herdecke


germany.gif

PostPosted: 2010-01-29, 11:48    (No subject) Reply with quoteBack to top

Bugfix for error:
Undefined subroutine &main::array called at /.../crondump.pl line 1121

Change line 1121 of msd_cron/crondump.pl
            @cad=array($commandDump);

to
            @cad=($commandDump);

_________________
Gruß / Greetings, DSB

Teigwaren heißen Teigwaren, weil sie Teig waren.
Diejenigen, die lautstark darüber diskutieren, warum es nicht geht, mögen bitte jene nicht stören, die es gerade tun.

OfflineView user's profileSend private messageSend e-mailVisit poster's website    
Display posts from previous:      
Post new topicThis topic is locked: you cannot edit posts or make replies.


 Jump to:   


Show permissions
Similar topics
Topic Author Forum Replies Posted
No new posts Ende des Projekts MySQLDumper Fabio Allgemeine Fragen zu MySQLDumper 7 2016-02-10, 07:52 View latest post
No new posts Ende des Projekts MySQLDumper DSB FAQ 0 2016-01-31, 18:17 View latest post
No new posts .csv - Datei mit mySQLDumper importie... torstenv MySQLDumper 1.24 1 2015-09-17, 13:50 View latest post
No new posts How to install mysqldumper in vestacp shaheryar MySQLDumper Downloads 1 2015-09-11, 15:11 View latest post
No new posts Wird mysqldumper weiter entwickelt? SwiRa Allgemeine Fragen zu MySQLDumper 1 2015-09-05, 23:41 View latest post

 
CrackerTracker © 2004 - 2016 CBACK.de

Powered by Orion based on phpBB © 2001, 2002 phpBB Group
CBACK Orion Style based on FI Theme
All times are GMT + 2 Hours

phpBB SEO