From c8c54c25e89ee5547af75fcbb909f82c703ccaac Mon Sep 17 00:00:00 2001 From: Yamil Suarez Date: Fri, 3 Jun 2011 00:36:35 -0400 Subject: [PATCH 1/1] Fixed DocBook mistakes introduced when adding "Exporting Report Templates Using phpPgAdmin" section --- .../report-exporting-report-templates-using-phppgadmin.xml | 4 ++-- 1.6/root.xml | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/1.6/reports/report-exporting-report-templates-using-phppgadmin.xml b/1.6/reports/report-exporting-report-templates-using-phppgadmin.xml index 08bd165872..7f434d51d6 100644 --- a/1.6/reports/report-exporting-report-templates-using-phppgadmin.xml +++ b/1.6/reports/report-exporting-report-templates-using-phppgadmin.xml @@ -5,7 +5,7 @@ Exporting Report Templates Using phpPgAdmin Once the data is exported. Database Administrators/Systems Administrators can easily import this data into the templates folder to make it available in the client. - + Dump the Entire Reports Template Table The data exported in this method can create issues importing into a different system if you do not have a matching folder and owner. This is going to export report templates created in your system. The most important fields for importing into the new system are name, description, and data. Data defines the actual structure of the report. The owner and folder fields will unique to the system they were exported from and will have to be altered to ensure they match the appropriate owner and folder information for the new system. @@ -23,7 +23,7 @@ - + Dump Data with an SQL Statement The following statement could be used to grab the data in the folder and dump it with admin account as the owner and the first folder in your system. SELECT 1 as owner, name, description, data, 1 as folder FROM reporter.template diff --git a/1.6/root.xml b/1.6/root.xml index 6b33ac4a21..255ed5a7a8 100755 --- a/1.6/root.xml +++ b/1.6/root.xml @@ -98,7 +98,7 @@ - + -- 2.43.2