| From: | Steve Midgley <science(at)misuse(dot)org> |
|---|---|
| To: | Suresh Raja <suresh(dot)rajaabc(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: extracting PII data and transforming it across table. |
| Date: | 2015-05-21 16:33:19 |
| Message-ID: | CAJexoS+kzEmHn2LqzQ2U+KP-wMjjRKQ0EC+KWSaYnimK5ifQsA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
I would update the IDs using SQL before dumping if possible. If necessary
clone the tables, adjust the IDs and then dump. SQL has better tools than
most languages/scripts to adjust values in columns across multiple
entities. Plus it should be easier to build some test queries in SQL to
validate that your ID adjustments were valid.
On Thu, May 21, 2015 at 9:27 AM, Suresh Raja <suresh(dot)rajaabc(at)gmail(dot)com>
wrote:
> Hi Folks:
>
> I'm looking at directions or help in extracting data from production and
> alter employee id information while extracting. But at the same time
> maintain referential integrity across tables. Is it possible to dump data
> to flat file and then run some script to change emp id data on all files.
> I'm looking for a easy solution.
>
> Thanks,
> -Suresh Raja
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Suresh Raja | 2015-05-21 16:51:31 | Re: extracting PII data and transforming it across table. |
| Previous Message | Suresh Raja | 2015-05-21 16:27:33 | extracting PII data and transforming it across table. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Suresh Raja | 2015-05-21 16:51:31 | Re: extracting PII data and transforming it across table. |
| Previous Message | Suresh Raja | 2015-05-21 16:27:33 | extracting PII data and transforming it across table. |