Prev: Adding support for SE-Linux security
Next: how to hack a webmail
From: "Little, Douglas" on 2 Dec 2009 15:19
Hi,
In sept 2009 there was a discussion of ragged csv import and import requirements.
I thought I'd add my requirements to the heap.

I'm working a QA solution for a dbms migration project that will import query output from a non PG database into PG, so we can compare query results between PG and the alternative db.
The query are supposed to have the same values, but many things can get in the way.

My QA queries return a result set (multiple rows/columns) for each query.

Copy improvements that would be useful
1. Copy to non-existent table - create it from the data type using most generic datatypes
2. provide column mapping function - from what I understand that the column list on a copy from is the target columns to load. I assume there must be a header record and the same columns in the
Data file.

The improvements discuss in the forum would be very helpful. Keep up the good work guys.

Doug Little
Sr. Data Warehouse Architect | Enterprise Data Management | Orbitz Worldwide
500 W. Madison, Suite 1000 Chicago IL 60661| Office 312.260.2588 | Fax 312..894.5164 | Cell 847-997-5741
Douglas.Little(a)orbitz.com<mailto:Douglas.Little(a)orbitz.com>

[cid:image002.jpg(a)01CA735A.7B428B90] orbitz.com<http://www.orbitz.com/> | ebookers.com<http://www.ebookers.com/> | hotelclub.com<http://www.hotelclub.com/> | cheaptickets.com<http://www.cheaptickets.com/> | ratestogo.com<http://www.ratestogo.com/> | asiahotels.com<http://www.asiahotels.com/>

 | 
Pages: 1
Prev: Adding support for SE-Linux security
Next: how to hack a webmail