Difference between revisions of "Pdm load"
(→Examples) |
(Undo revision 4152 by Agegeleruvy (Talk) - spam?) |
||
| (9 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Use pdm_load to | + | __NOTOC__ |
| + | [[Category:Commands]] | ||
| + | {{Global Header}} | ||
| + | {{Global Announcement}} | ||
| + | |||
| + | == Overview == | ||
| + | Use pdm_load to insert, update or remove data into the database and bypass the GUIs.<br> | ||
| + | pdm_load uses the SeviceDesk virtual DB Schema layer to access the physical database.<br> | ||
| + | Contrary to direct Database access by ODBC for example, each data change is directly propagated to all ServiceDesk processes. | ||
== Usage == | == Usage == | ||
| Line 64: | Line 72: | ||
| − | + | == Notes == | |
| − | + | When doing a pdm_load of a ca_xxxxxx table that contains references to another ca_xxxxxx table, the reference must be valid or the entry will not be loaded and an error generated. For example, if loading the ca_contact table, if the ca_location_uuid field contains references to the ca_location table, then the record that is being reference MUST exist in the ca_location table or that particular entry will not be loaded. A common scenario is to perform an extract of the production contact data and then load it into development. However if the contact tables has references to the ca_location table you will first need to do a load of the ca_location table to ensure that all the references from the ca_contact load are valid. And if the ca_location table has references to the ca_site table, you will need to do a load of ca_site to ensure all the references from the ca_location load are valid. | |
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 11:02, 26 November 2010
To discuss or ask questions about this article, select the discussion tab above.
Overview
Use pdm_load to insert, update or remove data into the database and bypass the GUIs.
pdm_load uses the SeviceDesk virtual DB Schema layer to access the physical database.
Contrary to direct Database access by ODBC for example, each data change is directly propagated to all ServiceDesk processes.
Usage
pdm_load -f [filename] [-a] [-c] [-e] [-h] [-i] [-m] [-v] [-r] [-u] [-x]
| Command | Description | Remarks |
|---|---|---|
| -a | update all matching data | |
| -c | check only, no change to data | |
| -e | treat escapes literally | |
| -h | help | |
| -i | insert only | |
| -m | notify domsrvr of mass update | |
| -v | verbose | |
| -r | remove | |
| -u | update only | |
| -x | use locale sensitive numeric input formats |
Examples
- A standard load. This load assumes that the file contains ids or uuids for all entries.
pdm_load -f extract.txt -v
- Using the -i to load data will force the creation of new ids and uuids. The file being loaded should be void of any id and uuid data.
pdm_load -f cnt_data.csv -i -v
- Removing some info (not shared by another application) from a file. Use the -r
pdm_load -f InfoToRemove.dat -r -v 2>load.err
Notes
When doing a pdm_load of a ca_xxxxxx table that contains references to another ca_xxxxxx table, the reference must be valid or the entry will not be loaded and an error generated. For example, if loading the ca_contact table, if the ca_location_uuid field contains references to the ca_location table, then the record that is being reference MUST exist in the ca_location table or that particular entry will not be loaded. A common scenario is to perform an extract of the production contact data and then load it into development. However if the contact tables has references to the ca_location table you will first need to do a load of the ca_location table to ensure that all the references from the ca_contact load are valid. And if the ca_location table has references to the ca_site table, you will need to do a load of ca_site to ensure all the references from the ca_location load are valid.
