Re: RE: SQL tools

Don,  You are correct that using sql to query the file and the like is just
a small part of what the data perspective gives us.  The features that are
contained in the perspective are nice.  The following is my take though.  We
are trying to get AS400 people to move to this GUI editor.  I think IBM
would like that to happen as well.

The problem is we have to have performance first and features later.  The
hard core green screen attics will not switch over to the editor because it
can do all these functions.  First of all 95 percent of the SQL actions
AS400 shops perform are probably select,insert, update etc...  The other
five percent might be one or a combination of these other features.

I want to be able to use sql to find out what is in my database first.  Then
when the need arises create an XML schema because a customer wants me to
send them an XML file or something to that effect.  I'm not saying that
there are not shops out there that use some of these features heavily.  I'm
saying the majority of them are not.

This perspective takes a long time to figure out how to get what you want.
I finally figured out that only when you use the filter upon creating a
connection will it pick up all the files in that particular library.  If you
try to not change the filter it only picks up the metadata etc... for those
files created via SQL.  You have to use the filter to get it to pick up
files created by DDS.  Then you move it to a folder.  Once there you can
select the statements folder and create a new sql statement.  The problem I
have with this is the thing keeps executing the sql command before I'm
finished.  I try to use the content assist and it takes forever.  Once I get
the sql statement to work I do not see any results.  It takes me a little
while to realize there are no records in the file.  Why didn't something
tell me there were zero records found?

Looking at it from my viewpoint it will not benefit me much at this point.
Looking at it from the project developer who must have these features then
it will work if the performance is not a problem.

I want the best of both worlds!  The great features that we only use once in
a while and the features that are mundane, but are needed and used the most.
But most of all I want the thing to work fast so I can talk everyone else I
work with into using the thing.

--
PAUL PENDLETON
"Don Yantzi" <yantzi@xxxxxxxxxx> wrote in
message
news:OF2A3B4576.7928C7B1-ON85256D35.0070AF23-85256D35.00736D35@xxxxxxxxxxxxx
om...
> Scott,
>
> I will look at updating the article for V5.0 and am also looking at
> creating a presentation on the database tools which we can post to the
> website.  I haven't played with the Quantum plug-in yet so I can't offer
> any comparison between it and the Database tooling in WDSc.  However I can
> provide some points on the functions in the Database tooling.  First to
> get started ...
>
> - yes, the data perspective is the central user interface for the Database
> tooling
> - yes, you need to create a Database connection to get started.  You do
> this by right clicking in the DB Servers view and selecting New
> Connection...
> - yes, the correct path for the class location is
>
C:\WDSC\iseries\eclipse\plugins\com.ibm.etools.iseries.toolbox_5.0.0\runtime
\jt400.jar
> - Make sure you specify a filter!!!  Schemas map to libraries on the
> iSeries so if you want to include a list of libraries just add them to the
> filter (make sure you change the operator to OR instead of AND.)  If you
> see nothing come back from creating the connection or the Workbench seems
> to hang it is likely because the filter is wrong.  By default the tool
> downloads metadata for the entire database which on the iSeries is quite
> big (hence why it looks like it hangs, come back in an hour or two and it
> will probably be finished.)
>
> Now that you have your connection, right click on the connection and
> select "Import To Folder".  This imports the database metadata into a
> local workspace project so you can continue to use it without being
> connected to the database.  Obviously one part of the database tooling is
> to look at the data, but this is really only a small part of the tooling.
> By importing the database metadata into the workspace it can be used by
> other tools like:
>
> - The graphical SQL editor to allow you write and test SQL statements
> (edit SQL graphically or manually)
> - Use the database tooling to define new tables in the database
> - Database Web pages wizard (uses the database information to create web
> pages to list, update, delete information from a database)
> - EJB tooling (advanced edition of WDSc)
> - XML tooling (generate an XML schema from a database definition, read
> records from a database into an XML document or write information from an
> XML doc to the database)
> - ...
>
> So in conclusion : )   The ability to look at the records in the database
> or to create an SQL statement is only a small part of the database tools.
> A much larger part is that other tools integrated into the Workbench use
> the information from the database tools to do other things.  It's all
> about integration : )
>
> If anyone is still having problems getting connected and creating an SQL
> statement please post them.
>
> Thanks.
>
> Don Yantzi
> WebSphere Development Studio Client for iSeries
> IBM Toronto Lab
> Phone: (905) 413-4476
> IBM internal:  IBMCA(yantzi)  -  Internet:
yantzi@xxxxxxxxxx
>
>
>
>
>
> "Scott Johnson" <sjohnson@xxxxxxxxxxxxx>
> Sent by: wdsci-l-bounces@xxxxxxxxxxxx
> 29/05/2003 12:24 PM
> Please respond to Websphere Development Studio Client for iSeries
>
>
>         To:     "'Websphere Development Studio Client for iSeries'"
> <wdsci-l@xxxxxxxxxxxx>
>         cc:
>         Subject:        RE: [WDSCI-L] RE: SQL tools
>
>
>
>
> I kind of knew it was 4.0, but did not know if there had been any changes
> with it for 5.0.  Maybe we can convince Phil to talk to the author and
> have
> them update it for ver 5.0.
>
> -- Scott
>
> > -----Original Message-----
> > From: wdsci-l-bounces@xxxxxxxxxxxx
> > [mailto:wdsci-l-bounces@xxxxxxxxxxxx]On
Behalf Of Samuel J Lennon
> > Sent: Thursday, May 29, 2003 11:06 AM
> > To: wdsci-l@xxxxxxxxxxxx
> > Subject: Re: [WDSCI-L] RE: SQL tools
> >
> >
> >    This appears to be for version 4.  In version 5 I found that the
> >    DBExplorer view is now named DBServers.  And to run the
> > built SQL you had
> >    to right click on it in the Outline pane.
> >
> >    I don't know how useful this will be.  I'll need to spend
> > more time and I
> >    need a 21" monitor to cope with all the windows...
> >
> >    Sam
> >
> >    >From: "Scott Johnson"
<SJOHNSON@xxxxxxxxxxxxx>
> >    >Reply-To: Websphere Development Studio Client for
> >    iSeries<WDSCI-L@xxxxxxxxxxxx>
> >    >To: "'Websphere Development Studio Client for iSeries'"
> >    <WDSCI-L@xxxxxxxxxxxx>,
<CODE400-L@xxxxxxxxxxxx>
> >    >Subject: [WDSCI-L] RE: SQL tools
> >    >Date: Thu, 29 May 2003 09:00:10 -0500
> >    >
> >    >
> >    >Here is an article on setting up and using the Data Perspective:
> >    >
> >    >http://eservercomputing.com/iseries/archives/index.asp?a=1&id=489
> >    >
> >    >
> >
>
> _______________________________________________
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
> mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.
>
>
> _______________________________________________
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/wdsci-l.
>