RE: Changing an SQL table (Best practices) -- MIDRANGE-L

Subject: RE: Changing an SQL table (Best practices)
From: "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 11 Jan 2007 16:20:16 -0600
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I recall a guy that had to make sure his SQL statements are backwards
compatible to a previous release, without having access to a machine on that
previous release.
I believe he used Syntax Check SQL Statement API:

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/qsqchks.htm

HTH

Elvis

Celebrating 10-Years of SQL Performance Excellence

-----Original Message-----
Subject: RE: Changing an SQL table (Best practices)

Is there some SQL verify API that these CM vendors could be using for 
Verify?

Rob Berendt

Follow-Ups:

RE: Changing an SQL table (Best practices) , rob

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.