Difference between revisions of "Pdm deref"
From SDU
Agegeleruvy (Talk | contribs) |
m (Reverted edits by Agegeleruvy (Talk); changed back to last version by Jc.oakgov) |
||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
__NOTOC__ | __NOTOC__ | ||
[[Category:Commands]] | [[Category:Commands]] | ||
| Line 16: | Line 8: | ||
For example, lets say you performed the following extract: | For example, lets say you performed the following extract: | ||
| − | '''pdm_extract -f | + | '''pdm_extract -f "SELECT id,category FROM Call_Req" > output.txt.''' |
The resulting extract would have the category entries displayed in their persid format such as pcat:400001. If you wanted to replace the category persid with the sym, the pdm_deref can perform that function. | The resulting extract would have the category entries displayed in their persid format such as pcat:400001. If you wanted to replace the category persid with the sym, the pdm_deref can perform that function. | ||
== Usage == | == Usage == | ||
| − | pdm_extract [-s] specfile [-c|-e|-r] [-d] [-h] [-n] [-p] [-u] [-v 1|2] | + | pdm_extract [-s] specfile [-c|-e|-r] [-d] [-h] [-n] [-p] [-u] [-v 1|2] <filename |
| − | + | <br> | |
{| | {| | ||
|- | |- | ||
| Line 60: | Line 52: | ||
| | | | ||
|- | |- | ||
| − | | -v | + | | -v <nowiki>[1|2]</nowiki> |
| verbose. 1 is brief and 2 prints to a log file. | | verbose. 1 is brief and 2 prints to a log file. | ||
| | | | ||
| Line 73: | Line 65: | ||
== Specfile Example== | == Specfile Example== | ||
A [[pdm_extract]] in the following format: | A [[pdm_extract]] in the following format: | ||
| − | + | <source lang=text>TABLE Call_Req | |
id category | id category | ||
| − | { | + | { "499998" ,"pcat:400001" } |
| − | { | + | { "499999" ,"pcat:400001" }</source>...will be change to this format: |
| − | + | <source lang=text>TABLE Call_Req | |
id category.sym | id category.sym | ||
| − | { | + | { "499998" ,"Sofware.Adobe Reader" } |
| − | { | + | { "499999" ,"Softtware.Adobe Writer" }</source>...by running a specfile containing the following SQL Statement: |
| − | + | <source lang=sql>Deref | |
{ | { | ||
input = category | input = category | ||
output = category.sym | output = category.sym | ||
| − | rule = | + | rule = "SELECT sym FROM Prob_Category WHERE persid=?" |
| − | } | + | }</source> |
== Examples == | == Examples == | ||
* Deref of a basic text file | * Deref of a basic text file | ||
| − | pdm_deref -s specfile.txt | + | pdm_deref -s specfile.txt < input.txt > output.txt |
Latest revision as of 05:28, 30 November 2010
To make corrections or additions to this article, select the edit tab above.
To discuss or ask questions about this article, select the discussion tab above.
To discuss or ask questions about this article, select the discussion tab above.
Overview
Use this command to replace data with data found in another table.
For example, lets say you performed the following extract: pdm_extract -f "SELECT id,category FROM Call_Req" > output.txt. The resulting extract would have the category entries displayed in their persid format such as pcat:400001. If you wanted to replace the category persid with the sym, the pdm_deref can perform that function.
Usage
pdm_extract [-s] specfile [-c|-e|-r] [-d] [-h] [-n] [-p] [-u] [-v 1|2] <filename
| Command | Description | Remarks |
|---|---|---|
| -s specfile | file containing SQL statement | |
| -c | csv output | |
| -e | csv output with double double quotes | |
| -r | informal report output | |
| -d | diagnostics | |
| -h | Help | |
| -p | preserve whitespace | |
| -u | no headers | |
| -v [1|2] | verbose. 1 is brief and 2 prints to a log file. | |
| filename | file to be processed |
Specfile Example
A pdm_extract in the following format: <source lang=text>TABLE Call_Req id category { "499998" ,"pcat:400001" } { "499999" ,"pcat:400001" }</source>...will be change to this format: <source lang=text>TABLE Call_Req id category.sym { "499998" ,"Sofware.Adobe Reader" }
{ "499999" ,"Softtware.Adobe Writer" }</source>...by running a specfile containing the following SQL Statement:
<source lang=sql>Deref { input = category output = category.sym rule = "SELECT sym FROM Prob_Category WHERE persid=?" }</source>
Examples
- Deref of a basic text file
pdm_deref -s specfile.txt < input.txt > output.txt
