|
----- Message from Edmund Reinhardt <edmund.reinhardt@xxxxxxxxxx> onhttp://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=11052
Thu, 30 Oct 2014 15:38:57 -0400 -----
To:
Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject:
Re: [WDSCI-L] Running SQL scripts
I have thoughts about that too.
On that way from RDi to SQL script editor
Strip DECLARE .. prefix and put in comment
Let the developer play with just the SELECT statement
On the way back, prepend from the DECLARE comment
Just thoughts
BTW, would you see what I proposed as a sufficient solution to RFE
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=11086
Regarding the RFE on visual explain.
When I was discussing this with Mark Anderson he didn't think thatexplain
developers had the authority or interest or expertise to use visual
to optimize queries beyond noticing the need to index certain tables.But
I see 46 votes on this RFE. Are developers making active use of Visualrather
Explain?
Regards,
Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i
Phone: 1-905-413-3125 | Home: 1-905-854-6195
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200
Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham,
ON L6G 1C7
Find me on: Canada
From: Buck Calabro <kc2hiz@xxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Date: 30/10/2014 03:15 PM
Subject: Re: [WDSCI-L] Running SQL scripts
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
On 10/30/2014 2:56 PM, Jon Everton wrote:
Create a stored procedure using input parameters with the table andschema
name. Use the SQL function REPLACE to put your variables into the SQL
statement. Send me an email and I'll send you an example if this
poorfeatures
explanation confuses you.
That's clear Jon, thanks. This thread is morphing into a discussion on
integrating Data Studio with RDi. Imagine you have an existing SQLRPGLE
program with a DECLARE CURSOR as below. You'd like to make some changes
to that SQL statement, what does one do?
Rectangle select, copy, tab to Data Studio, paste. Replace the host
variables with literals, test. Edit, test, repeat. When happy with the
new SQL statement, copy in Data Studio, tab to RDi, select, paste.
Adjust formatting. Save, compile, test. Forgot to replace literals,
wonder why program doesn't work. Replace literals with host variables.
Save, compile, test.
It's better than a sharp stick in the eye, but that's a low bar :-)
date: Thu, 30 Oct 2014 14:30:16 -0400
from: Buck Calabro <kc2hiz@xxxxxxxxx>
subject: Re: [WDSCI-L] Running SQL scripts
On 10/30/2014 2:10 PM, Edmund Reinhardt wrote:
There is a small subset of IBM Data Studio which is shipped with RDi.
Now that IBM Data Studio itself is free, you can get the full
IBMof the product. The SQL running/editing/diagramming is relevant to
IBM i. The query tuning is not since it is geared to LUW DBW (not
i).eventually,
I am thinking about developing better integration with RDi
couldandso I am following this thread with interest.
So if there was an easy way to get embedded SQL into an SQL script
editor in IBM Data Studio would this help write, test queries?
Mad utopian dreamer alert!
Given:
select SYSTEM_COLUMN_NAME, DATA_TYPE, "LENGTH", NUMERIC_SCALE,
COLUMN_TEXT, IS_NULLABLE, "CCSID", SYSTEM_TABLE_NAME,
SYSTEM_TABLE_SCHEMA, COLNO
from SYSCOLUMNS
where SYSTEM_TABLE_NAME = :REF_FILE and
SYSTEM_TABLE_SCHEMA = :REF_LIBR;
I would love to have the test/debug tool/IDE be able to 'declare'
variables :REF_FILE and :REF_LIBR as well as populate them with values
then execute this code as-is. Once my SQL is working properly, I
thenliterals
cut / paste it back into my HLL as-is without having to remove
and
replace them with host variables.option
Similar to the ability SDA has to populate fields for testing (STRSDA
3).
--
--buck
'I had nothing to offer anybody except my own confusion' - Jack Kerouac
--
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.