pergamonmu:vendor:importsqldump
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
pergamonmu:vendor:importsqldump [2017/08/31 19:03] admin |
pergamonmu:vendor:importsqldump [2017/08/31 19:34] (current) admin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Import SQL Dump ====== | ====== Import SQL Dump ====== | ||
| + | |||
| + | //This feature is only available from v1.0.96 onwards.// | ||
| The **Import SQL Dump** facility is provided to import a SQL Dump file that was generated using the [[pergamonmu:vendor:exportsqldump|Export SQL Dump]] facility on the same or like-Pergamon installation, such as the merger of several initial cataloging databases on different machines and without the availability of a networked database. | The **Import SQL Dump** facility is provided to import a SQL Dump file that was generated using the [[pergamonmu:vendor:exportsqldump|Export SQL Dump]] facility on the same or like-Pergamon installation, such as the merger of several initial cataloging databases on different machines and without the availability of a networked database. | ||
| Line 9: | Line 11: | ||
| * Circulations\\ \\ | * Circulations\\ \\ | ||
| - | The the filename is irrelevant - the file type is identified from internal data within the file. | + | The filename is irrelevant - the file type is identified from internal data within the file. |
| One or more of these files can be imported - a cataloging exercise for example, need only use Item SQLDump files. There is no requirement to either generate or import all three. | One or more of these files can be imported - a cataloging exercise for example, need only use Item SQLDump files. There is no requirement to either generate or import all three. | ||
pergamonmu/vendor/importsqldump.1504206236.txt.gz · Last modified: 2017/08/31 19:03 by admin
Page Tools
