Mercurial > repos > bgruening > pg_dump
comparison pg-dump.xml @ 0:68988da52803 draft default tip
planemo upload for repository https://github.com/bgruening/galaxytools/tools/pgtools commit ab93c4c70fa487e55a24863a7786e102e7d92272
author | bgruening |
---|---|
date | Wed, 24 Apr 2019 06:10:53 -0400 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 0:68988da52803 |
---|---|
1 <tool id="pg_dump" name="Dump" version="@PG_VERSION@"> | |
2 <description>postgres database</description> | |
3 <macros> | |
4 <import>macros.xml</import> | |
5 </macros> | |
6 <expand macro="requirements" /> | |
7 <command detect_errors="aggressive"><![CDATA[ | |
8 @UNTAR_INFILE@ && | |
9 @PG_START@ && | |
10 pg_dump "\$(pglite url -d ./postgresql)" $no_owner -f '$outfile' && | |
11 @PG_STOP@ | |
12 ]]> | |
13 </command> | |
14 <inputs> | |
15 <param name="infile" type="data" format="postgresql" label="Input database" /> | |
16 <param name="no_owner" type="boolean" truevalue="--no-owner" falsevalue="" value="--no-owner" | |
17 label="Do not emit owner statements" | |
18 help="Do not output commands to set ownership of objects to match the original database. This is turned on by default because it is expected that the pg_dump tool will be used when exporting the data for use in a system external to Galaxy. Thus the authorization statements are likely to be different so we remove this."/> | |
19 </inputs> | |
20 <outputs> | |
21 <data format="txt" name="outfile" /> | |
22 </outputs> | |
23 <tests> | |
24 <test> | |
25 <param value="pg_import_result1.pg.tar.bz2" name="infile"/> | |
26 <output file="init-galaxy-db.sql.in" name="outfile" ftype="txt" /> | |
27 </test> | |
28 </tests> | |
29 <help> | |
30 <![CDATA[ | |
31 pg_dump | |
32 ------- | |
33 | |
34 This tool produces a SQL dump of the database file, compatible with import into external postgres databases. | |
35 | |
36 @HELP_FOOTER@ | |
37 | |
38 ]]> | |
39 </help> | |
40 <expand macro="citations" /> | |
41 </tool> |