RE: Percolating QC changes -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Percolating QC changes
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Fri, 3 Mar 2017 17:10:08 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

To clarify, by "table data" I mean PF's containing static data. A typical QC report could necessitate 100's of DB row changes.

-----Original Message-----
From: Justin Taylor
Sent: Friday, March 03, 2017 8:33 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: Percolating QC changes

OK, so I'm hearing that for source, just merge and deal with the conflicts. What about table data?

Follow-Ups:

Re: Percolating QC changes , David Gibbs

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.