Pdm load - Revision history

Bartosz: Undo revision 4152 by Agegeleruvy (Talk) - spam?

2010-11-26T11:02:14Z

Undo revision 4152 by Agegeleruvy (Talk) - spam?

Agegeleruvy at 03:14, 24 November 2010

2010-11-24T03:14:19Z

Gityerfix at 04:14, 27 July 2008

2008-07-27T04:14:31Z

Gityerfix at 05:02, 26 July 2008

2008-07-26T05:02:23Z

Gityerfix at 16:37, 18 July 2008

2008-07-18T16:37:33Z

Mikelm at 15:28, 3 July 2008

2008-07-03T15:28:28Z

Gityerfix at 13:20, 7 March 2008

2008-03-07T13:20:36Z

Gityerfix at 18:46, 22 February 2008

2008-02-22T18:46:21Z

Admin at 21:16, 27 January 2008

2008-01-27T21:16:26Z

Admin: /* Examples */

2008-01-27T21:14:28Z

‎Examples

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Commands]]
@@ Line 13: / Line 5: @@
 == Overview ==
-Use pdm_load to insert, update or remove data into the database and bypass the GUIs.&lt;br&gt;
+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.&lt;br&gt;
+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 ==
 pdm_load -f [filename] [-a] [-c] [-e] [-h] [-i] [-m] [-v] [-r] [-u] [-x]
-&lt;br&gt;
+<br>
 {|
 |-
@@ Line 77: / Line 69: @@
 * Removing some info (not shared by another application) from a file. Use the -r
-  pdm_load -f InfoToRemove.dat -r -v 2&gt;load.err
+  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.

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Commands]]
@@ Line 5: / Line 13: @@
 == Overview ==
-Use pdm_load to insert, update or remove data into the database and bypass the GUIs.<br>
+Use pdm_load to insert, update or remove data into the database and bypass the GUIs.&lt;br&gt;
-pdm_load uses the SeviceDesk virtual DB Schema layer to access the physical database.<br>
+pdm_load uses the SeviceDesk virtual DB Schema layer to access the physical database.&lt;br&gt;
 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]
-<br>
+&lt;br&gt;
 {|
 |-
@@ Line 69: / Line 77: @@
 * Removing some info (not shared by another application) from a file. Use the -r
-  pdm_load -f InfoToRemove.dat -r -v 2>load.err
+  pdm_load -f InfoToRemove.dat -r -v 2&gt;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.

@@ Line 1: / Line 1: @@
 __NOTOC__
 [[Category:Commands]]
-<div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br>
+{{Global Header}}
-To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>
+{{Global Announcement}}
 == Overview ==

@@ Line 1: / Line 1: @@
 [[Category:Commands]]
 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>
@@ Line 69: / Line 74: @@
 == 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.

@@ Line 1: / Line 1: @@
 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>
@@ Line 68: / Line 69: @@
 == 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.
 ----
-<div align='center'><font color="red">To make corrections or additions to this article, select the ''edit'' tab above.<br>
+<div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br>
 To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>

← Older revision		Revision as of 15:28, 3 July 2008
Line 1:		Line 1:
−	Use pdm_load to ~~load information directly~~ into the database and bypass the GUIs.	+	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 ==

← Older revision		Revision as of 13:20, 7 March 2008
Line 65:		Line 65:

	== Notes ==		== 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~~. This is a scenario could be seen when taking production data and loading it in a development environment~~. 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.	+	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.

← Older revision		Revision as of 18:46, 22 February 2008
Line 62:		Line 62:
	* Removing some info (not shared by another application) from a file. Use the -r		* Removing some info (not shared by another application) from a file. Use the -r
	pdm_load -f InfoToRemove.dat -r -v 2>load.err		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. This is a scenario could be seen when taking production data and loading it in a development environment. 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.

@@ Line 55: / Line 55: @@
 == Examples ==
 * A standard load. This load assumes that the file contains ids or uuids for all entries.
-<source lang=dos>pdm_load -f extract.txt -v</source>
+ 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.