Author: plavin
Date: 2006-12-11 15:13:14 +0100 (Mon, 11 Dec 2006)
New Revision: 4204
Log:
Use &ddash; - thanks Jon
Modified:
trunk/migration-toolkit/scripted-migration.xml
Modified: trunk/migration-toolkit/scripted-migration.xml
===================================================================
--- trunk/migration-toolkit/scripted-migration.xml 2006-12-11 09:52:52 UTC (rev 4203)
+++ trunk/migration-toolkit/scripted-migration.xml 2006-12-11 14:13:14 UTC (rev 4204)
Changed blocks: 9, Lines Added: 9, Lines Deleted: 9; 3557 bytes
@@ -157,7 +157,7 @@
<para>
Open the Lua script that you generated during migration and find
- the <literal>-- Set source connection</literal> line. Immediately
+ the <literal>&ddash; Set source connection</literal> line. Immediately
below this line is the code that defines the source connection of
the schema that is being migrated.
</para>
@@ -202,7 +202,7 @@
</para>
<para>
- Below the <literal>-- set struct and types</literal> line find the
+ Below the <literal>&ddash; set struct and types</literal> line find the
definition of the data types used so far. A
<literal>sourceConnection</literal> is a struct derived from the
<literal>db.mgmt.Connection</literal> structure.
@@ -213,7 +213,7 @@
<para>
The parameters and the modules used for a
<literal>targetConnection</literal> are shown beneath the
- <literal>--Set target connection</literal> line. After examining a
+ <literal>&ddash;Set target connection</literal> line. After examining a
<literal>sourceConnection</literal> you should quickly be able to
understand a <literal>targetConnection</literal>. The same applies
to the structs and data types used by the
@@ -230,7 +230,7 @@
<para>
The conversion of the source schema to a MySQL schema occurs in
- the lines immediately following the comment <literal>-- Do the
+ the lines immediately following the comment <literal>&ddash; Do the
reverse engineering</literal>. This calls the GRT reverse
engineering module to convert from the current schema type to the
target type.
@@ -258,7 +258,7 @@
<title>Migration Methods</title>
<para>
- The code following the comment <literal>-- Migration methods and
+ The code following the comment <literal>&ddash; Migration methods and
ignore list</literal> invokes the migration module appropriate to
the source database.
</para>
@@ -310,7 +310,7 @@
tab of the Objects tree, you may query an object from
the command line in the GRT shell.
For example, in the code following the comment
- <literal>-- Set object mappings and do migration</literal>
+ <literal>&ddash; Set object mappings and do migration</literal>
a <literal>mappingdefaults</literal> object is created by
the <literal>grtV.setGlobal</literal> method.
</para>
@@ -331,7 +331,7 @@
cases you should see a schema mapping.
</para>
<para>
- Beneath the <literal>-- update _ids</literal> comment
+ Beneath the <literal>&ddash; update _ids</literal> comment
the migration methods are copied to a local variable
and then executed.
<remark>[PL]More info.</remark>
@@ -346,7 +346,7 @@
<para>
The target schema is created following the
- <literal> Generate and execute sql create statements</literal>.
+ <literal>&ddash; Generate and execute sql create statements</literal>.
If you chose to create
</para>
@@ -360,7 +360,7 @@
<para>
The target schema is populated following the
- <literal> Bulk data transfer</literal> comment.
+ <literal>&ddash; Bulk data transfer</literal> comment.
If you chose to create
</para>
</section-->
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4204 - trunk/migration-toolkit | plavin | 11 Dec |
