Free mysqldump software for linux

mysqlrowcopy is a tool that generates insert statements from result sets. It produces output similar to what might result from running mysqldump on a single SELECT query.

This project helps eliminate some of the tedium of moving data between QA and production MySQL databases.

Build:

To build mysqlrowcopy, you should run:

./configure
make

A mysqlrowcopy and mysqlrowcopy.debug file are created. They have identical functionality, the .debug version simply has debugging symbols built in (for gdb).

Since mysqlrowcopy is probably going to be I/O bound with modest CPU and RAM usage, the only reason to even build a 64-bit version is to work around potential issues in dynamic linking 32-bit binaries against 64-bit libraries.

RECIPES

1. Migrating a MySQL user account reaper from QA server to a production server.

e.g. MySQL database server qa3.example.com to prod1.example.com:

$ mysqlrowcopy -h qa3.example.com
SELECT * FROM db WHERE User = "reaper" mysql db > reaper.sql
$ mysql -h prod1.example.com mysql < reaper.sql

You could of course simply pipe the output of mysqlrowcopy into mysql and skip the intermediate file.

(Dont forget to RELOAD PRIVILEGES afterwards)

2. Keep your test environment up to date. Populate it with production data every 24 hours. You could run this sequence from cron once a day:

$ mysqlrowcopy -h finance-db.example.com
SELECT * FROM stocks WHERE modified > DATE_SUB(NOW(),INTERVAL 24 HOUR)
finance stocks > day-stocks.sql

$ cat day-stocks.sql | mysql -h finance-test.example.com finance

3. Copy data between tables on different servers that have some similar fields.

Youve got common data in table Zip on a production database:

mysql> desc Zip;
+-------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------+-------------+------+-----+---------+-------+
| ZIPCode | varchar(5) | | PRI | | |
| ZIPCodeType | char(1) | YES | | NULL | |
| City | varchar(32) | YES | | NULL | |
| CityType | char(1) | YES | | NULL | |
| State | varchar(32) | YES | | NULL | |
| StateCode | char(3) | YES | | NULL | |
| AreaCode | char(3) | YES | | NULL | |
| Latitude | varchar(12) | YES | | NULL | |
| Longitude | varchar(12) | YES | | NULL | |
+-------------+-------------+------+-----+---------+-------+
9 rows in set (0.00 sec)

And youve got table ZipPosition in a research database:

mysql> desc ZipPosition;
+-------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------+-------------+------+-----+---------+-------+
| ZIPCode | varchar(5) | | | | |
| Latitude | varchar(12) | YES | | NULL | |
| Longitude | varchar(12) | YES | | NULL | |
+-------------+-------------+------+-----+---------+-------+
3 rows in set (0.00 sec)

You want to load data from production Zip into research ZipPosition.

$ mysqlrowcopy -h production SELECT ZIPCode,Latitude,Longitude common ZipPosition > pos.sql
$ cat pos.sql | mysql -h qa research

Note how we specify ZipPosition on the first line to tell mysqlrowcopy what the destination table is going to be.

MySQL Backup for lazy sysadmins (mysqlblasy) is a Perl script for automating MySQL database backups. It uses "mysqldump" for dumping mysql databases to the files sytem. MySQL Backup for lazy sysadmins program was written with automated usage in mind.
For example, it is silent during operation, and only produces noise on errors/problems. It rotates backups automatically to prevent the backup disk from getting full when the administrator is on vacation (or is lazy).
Main features:
- syslog facility
- unix output (loglevels, errors to stderr)
- dump some or all databases from a database instance
- compress dumps (using gzip,bzip2 or perl modules)
- backup rotation to avoid disc overflow
- no shell on external commands!
- can be run as unpriviledged user
- perfect for cron jobs

StuffDawg project is a simple PHP-driven application which helps to catalog information about your important material items (such as your computer, for instance)) in case such items get lost, stolen, or otherwise destroyed. PHP mysqli support required, as is MySQL 5.
This version is basically functional. I need to add some better mechanisms of finding your stuff in the database (such as a search feature). There is also NO security mechanisms in place; it was designed to be run on a private network, such as a home LAN. I may add some security later, however, but nothing too extravagant.
One of the reasons I wanted to write this software was to get some experience with BLOBs in a database. Granted, it is slow and ugly (perhaps the Blob Streaming Project can speed things along when it comes to fruition), but I wanted to make sure there was a sort of simple and atomic datastore for the information. This way, all you need to do is run a mysqldump and put that somewhere. Even if, for some reason, the software disappears, you still have a database you can run queries on, etc. Besides, it made things much simpler on code.
Installation:
To install StuffDawg, you need to do the following:
- Unpack it (you must have figured that one out already, eh? :)
- Create a database to store the tables. Currently, there is no way to define a table-prefix. Maybe Ill implement that later.
- Import the schema.sql file into this new database, for example"
# mysql StuffDawg < schema.sql
- Create a database user for StuffDawg to use, of course.
- Edit classes/db.class.php and configure your database connection information by filling out the $username, $password, $hostname, and $database variables.
- The Smarty Tempalte Engine has been packaged with StuffDawg. If you prefer to use a different version than the one included, edit the global.inc.php file in the htdocs directory and configure to your liking.
- Make sure your web-server has read access to the directories and write access to the templates_c and cache directories.
- Configure yuor web-server to server content from the htdocs directory.
Enhancements:
- This release adds better image scaling, adds more intelligence to the templates, and fixes a few minor bugs.

JdbcTool project is a collection of command line utilities for making your life easy when working with Java JDBC databases. Included are:

jdbctool:

An interactive command line tool for executing SQL statements.

jdbcdump:

Dump the contents of a database as SQL statements into a file, like mysqldump.

jdbcload

Execute SQL statements from a file (the opposite of jdbcdump)

Currently, only HSQLDB is supported.

PyLucid project is a lightweight, OpenSource ( GPL 2.x or newer ) content management system ( CMS ) written in pure Python CGI.
Nearly all output can be customized. No shell account is needed. To run PyLucid you need a standard Webserver with Python (at least v2.2.1) CGI and MySQL ( mySQLdb ). (Based on the PHP lucidCMS).
Main features:
Characteristics
- poormans_modrewrite: normal-URLs without URL-Parameter ( to see on http://www.jensdiemer.de )
- double side names by absolute path possible
- secure JavaScript-md5 Login - safe Login, also without HTTPs/SSL
functions
- < lucidFunction:SourceCode > integrate Source-Files from local Webserver in the CMS page
- < lucidFunction:RSS > integrate RSS feed in the CMS page
adaptability
- edits from internal sides (Login, all forms to change from Styles, Templates etc..)
- administration Sub menu
basis
- pages, stylesheets, templates create/edit/delete
- searching
- SiteMap
- list of the newest changes
- menu
other
- see interna, inclusive SQL tables overview with optimization of the tables
- owner slimmer tinyTextile
- MySQLdump - Backup of database data
Whats New in 0.7.1 Stable Release:
- Using the new highlighter system pygments erstwhile PyKleur (LGPL)
- Using tinyTextile inline Sourcecode (with ...)
- Sourcecode-Plugin (Include local sourcecode file into your page.)
- New: RSS feed Generator Plugin
- Update the local internal pages files (for easier distribution of PyLucid)
- Many Bugfixes
Whats New in 0.8 Alpha 2 Development Release:
- Inline Editing with template tag list and tinyTextile help page.
- new reimplemented: create a cms page, delete pages and "Select a page to edit it".
- besser _install section login.
- CMS page view cache.
- better update routines.