« back to all changes in this revision
Viewing changes to docs/clients/drizzledump.rst
- browse files at revision 1994.4.81
- compare with another revision
- compare with revision 1833
- download diff
- download tarball
- view history from revision 1994.4.81
- Committer: Marisa Plumb
- Date: 2011-02-20 19:44:49 UTC
- mto: (2193.1.1 build) (2215.1.1 build) (2227.1.3 build) (2235.2.4 build)
- mto: This revision was merged to the branch mainline in revision 2194.
- Revision ID: marisa.plumb@gmail.com-20110220194449-d07mwzaz1731a5q4
edits
- files modified:
- docs/clients/drizzledump.rst
added
removed
docs/clients/drizzledump.rst
4
4
Synopsis
5
5
--------
6
6
7
:program:`drizzledump` [:ref:`OPTIONS <drizzledump-options-label>`] *database* [*tables*]
8
9
:program:`drizzledump` [:ref:`OPTIONS <drizzledump-options-label>`] :option:`--databases` *DB1* [*DB2* *DB3*...]
10
11
:program:`drizzledump` [:ref:`OPTIONS <drizzledump-options-label>`] :option:`--all-databases`
7
**drizzledump** [*OPTIONS*] *database* [*tables*]
8
9
**drizzledump** [*OPTIONS*] *--databases* [*OPTIONS*] *DB1* [*DB2* *DB3*...]
10
11
**drizzledump** [*OPTIONS*] *--all-databases* [*OPTIONS*]
12
12
13
13
Description
14
14
-----------
24
24
Any binary data in tables will be converted into hexadecimal output so that it
25
25
does not corrupt the dump file.
26
26
27
.. _drizzledump-options-label:
28
29
27
Drizzledump options
30
28
-------------------
31
29
32
30
The :program:`drizzledump` tool has several available options:
33
31
34
.. option:: --all-databases, -A
35
36
Dumps all databases found on the server apart from ``information_schema`` and
37
``data_dictionary`` in Drizzle and ``information_schema``,
38
``performance_schema`` and ``mysql`` in MySQL.
39
40
.. option:: --force, -f
32
.. option:: -A, --all-databases
33
34
Dumps all databases found on the server apart from *information_schema* and
35
*data_dictionary* in Drizzle and *information_schema*, *performance_schema*
36
and *mysql* in MySQL.
37
38
.. option:: -f, --force
41
39
42
40
Continue even if we get an sql-error.
43
41
44
.. option:: --help, -?
42
.. option:: -?, --help
45
43
46
44
Show a message with all the available options.
47
45
48
.. option:: --lock-all-tables, -x
46
.. option:: -x, --lock-all-tables
49
47
50
48
Locks all the tables for all databases with a global read lock. The lock is
51
49
released automatically when :program:`drizzledump` ends.
56
54
Creates a consistent snapshot by dumping the tables in a single transaction.
57
55
During the snapshot no other connected client should use any of the
58
56
following as this will implicitly commit the transaction and prevent the
59
consistency:
60
61
.. code-block:: mysql
57
consistency::
62
58
63
59
ALTER TABLE
64
60
DROP TABLE
81
77
Show progress of the dump every *rows* of the dump. Requires
82
78
:option:`--verbose`
83
79
84
.. option:: --verbose, -v
80
.. option:: -v, --verbose
85
81
86
82
Sends various verbose information to stderr as the dump progresses.
87
83
84
.. option:: --skip-create
85
86
Do not dump the CREATE TABLE / CREATE DATABASE statements.
87
88
88
.. option:: --skip-extended-insert
89
89
90
Dump every row on an individual line. For example:
91
92
.. code-block:: mysql
90
Dump every row on an individual line. For example::
93
91
94
92
INSERT INTO `t1` VALUES (1,'hello');
95
93
INSERT INTO `t1` VALUES (2,'world');
104
102
105
103
.. option:: --add-drop-database
106
104
107
Add ``DROP DATABASE`` statements before ``CREATE DATABASE``.
105
Add `DROP DATABASE` statements before `CREATE DATABASE`.
108
106
109
107
.. option:: --compact
110
108
112
110
:option:`--skip-add-drop-table`, :option:`--skip-disable-keys`
113
111
and :option:`--skip-add-locks`.
114
112
115
.. option:: --databases, -B
113
.. option:: -B, --databases
116
114
117
115
Dump several databases. The databases do not need to follow on after this
118
116
option, they can be anywhere in the command line.
119
117
120
.. option:: --skip-disable-keys, -K
118
.. option:: -K, --skip-disable-keys
121
119
122
Do not dump the statements ``ALTER TABLE ... DISABLE KEYS`` and
123
``ALTER TABLE ... ENABLE KEYS``
120
Do not dump the statements `ALTER TABLE ... DISABLE KEYS` and
121
`ALTER TABLE ... ENABLE KEYS`
124
122
125
123
.. option:: --ignore-table table
126
124
127
Do not dump specified table, needs to be in the format ``database.table``.
125
Do not dump specified table, needs to be in the format `database.table`.
128
126
Can be specified multiple times for multiple tables.
129
127
130
128
.. option:: --insert-ignore
131
129
132
Add the ``IGNORE`` keyword into every ``INSERT`` statement.
130
Add the `IGNORE` keyword into every `INSERT` statement.
133
131
134
132
.. option:: --no-autocommit
135
133
136
Make the dump of each table a single transaction by wrapping it in ``COMMIT``
134
Make the dump of each table a single transaction by wrapping it in `COMMIT`
137
135
statements.
138
136
139
.. option:: --no-create-db, -n
137
.. option:: -n, --no-create-db
140
138
141
Do not dump the ``CREATE DATABASE`` statements when using
139
Do not dump the `CREATE DATABASE` statements when using
142
140
:option:`--all-databases` or :option:`--databases`.
143
141
144
.. option:: --skip-create, -t
145
146
Do not dump the ``CREATE TABLE`` statements.
147
148
.. option:: --no-data, -d
142
.. option:: -t, --skip-create
143
144
Do not dump the `CREATE TABLE` statements.
145
146
.. option:: -d, --no-data
149
147
150
148
Do not dump the data itself, used to dump the schemas only.
151
149
152
150
.. option:: --replace
153
151
154
Use ``REPLACE INTO`` statements instead of ``INSERT INTO``
152
Use `REPLACE INTO` statements instead of `INSERT INTO`
155
153
156
154
.. option:: --destination-type type (=stdout)
157
155
208
206
mangled data. This is because MySQL will convert the data to UTF8 on the way
209
207
out to drizzledump and you effectively get a double-conversion to UTF8.
210
208
211
This typically happens with PHP apps that do not use ``SET NAMES``.
209
This typically happens with PHP apps that do not use 'SET NAMES'.
212
210
213
211
In these cases setting this option will retrieve the data as you see it in your
214
212
application.
215
213
216
214
.. versionadded:: 2011-01-31
217
215
218
.. option:: --host, -h hostname (=localhost)
216
.. option:: -h, --host hostname (=localhost)
219
217
220
218
The hostname of the database server.
221
219
222
.. option:: --user, -u username
220
.. option:: -u, --user username
223
221
224
222
The username for the database server.
225
223
226
.. option:: --password, -P password
224
.. option:: -P, --password password
227
225
228
226
The password for the database server.
229
227
230
.. option:: --port, -p port (=4427)
228
.. option:: -p, --port port (=3306,4427)
231
229
232
The port number of the database server.
230
The port number of the database server. Defaults to 3306 for MySQL protocol
231
and 4427 for Drizzle protocol.
233
232
234
233
.. option:: --protocol protocol (=mysql)
235
234
244
243
Backups using Drizzledump
245
244
-------------------------
246
245
247
Backups of a database can be made very simply by running the following:
248
249
.. code-block:: bash
250
251
$ drizzledump --all-databases > dumpfile.sql
252
253
This can then be re-imported into drizzle at a later date using:
254
255
.. code-block:: bash
256
257
$ drizzle < dumpfile.sql
246
Backups of a database can be made very simply by running the following::
247
248
$ drizzledump --all-databases > dumpfile.sql
249
250
This can then be re-imported into drizzle at a later date using::
251
252
$ drizzle < dumpfile.sql
258
253
259
254
MySQL Migration using Drizzledump
260
255
---------------------------------
269
264
270
265
.. warning::
271
266
272
:program:`drizzledump` will by default try to connect via. port 4427 so to
273
connect to a MySQL server a port (such as 3306) must be specified.
267
:program:`drizzledump` will by default try to connect via port 4427. To
268
connect to a MySQL server, a port (such as 3306) must be specified.
274
269
275
270
So, simply connecting to a MySQL server with :program:`drizzledump` as follows
276
will give you a Drizzle compatible output:
277
278
.. code-block:: bash
279
280
$ drizzledump --all-databases --host=mysql-host --port=3306 --user=mysql-user --password > dumpfile.sql
271
will give you a Drizzle compatible output::
272
273
$ drizzledump --all-databases --host=mysql-host --port=3306 --user=mysql-user --password > dumpfile.sql
281
274
282
275
Additionally :program:`drizzledump` can now dump from MySQL and import directly
283
into a Drizzle server as follows:
284
285
.. code-block:: bash
286
287
$ drizzledump --all-databases --host=mysql-host --port=3306 --user=mysql-user --password --destination-type=database --desination-host=drizzle-host
276
into a Drizzle server as follows::
277
278
$ drizzledump --all-databases --host=mysql-host --port=3306 --user=mysql-user --password --destination-type=database --desination-host=drizzle-host
288
279
289
280
.. note::
290
281
311
302
* mediumblob -> blob
312
303
* longblob -> blob
313
304
* year -> int
314
* set -> text [1]_
315
* date/datetime default 0000-00-00 -> default NULL [2]_
316
* date/datetime NOT NULL columns -> NULL [2]_
317
* any date data containing 0000-00-00 -> NULL [2]_
318
* time -> int of the number of seconds [3]_
319
* enum-> DEFAULT NULL [4]_
305
* set -> text
306
* date/datetime default 0000-00-00 -> default NULL (Currently, ALL date columns have their DEFAULT set to NULL on migration)
307
* date/datetime NOT NULL columns -> NULL
308
* any date data containing 0000-00-00 -> NULL
309
* time -> int of the number of seconds [1]_
310
* enum-> DEFAULT NULL
320
311
321
312
.. rubric:: Footnotes
322
313
323
.. [1] There is currently no good alternative to SET, this is simply to preserve
324
the data in the column. There is a new alternative to SET to be included
325
at a later date.
326
327
.. [2] Currently, ALL date columns have their DEFAULT set to NULL on migration.
328
This is so that any rows with 0000-00-00 dates can convert to NULL.
329
330
.. [3] This prevents data loss since MySQL's TIME data type has a range of
314
.. [1] This prevents data loss since MySQL's TIME data type has a range of
331
315
-838:59:59 - 838:59:59, and Drizzle's TIME type has a range of
332
00:00:00 - 23:59:59.
333
334
.. [4] This is so that empty entries such as '' will convert to NULL.
316
00:00:00 - 23:59:61.999999.
Loggerhead is a web-based interface for Breezy
Version: 2.0.1