|
From: Robert M. <rob...@gm...> - 2009-05-28 02:23:52
|
Chris,
I am not aware of any further efforts from Joe McDonald on this issue.
I read in the DB2 LUW to iSeries porting guide (attached) that most
interfaces allow you to specify naming property as "system" or "sql", so I
suppose the driver allows for this as well - although I have no access
to an iSeries system to confirm this. I would guess that a simple
work-around could be to specify "sql" as the value for the "naming"
driver property - correct? In any case, the SQL code in the
plugin assumes the "." is the qualifier separator, which works great on
LUW DB2 but not so much on iSeries. The trick to making this work
automatically in both platforms - based on session - would be to find
a JDBC API that exposes the naming setting, or at least the character
to be used in qualified names. I also read that leaving off the schema
qualifier prefix would cause DB2 to search through all it's catalogs for
the object, but this doesn't seem to be a very efficient approach. So,
without a test system to try out my ideas, I am a bit limited in how I
can help. You could help by doing some digging to determine a
reliable way to determine naming value ("system" or "sql"). For
example, can this be inferred from the driver property. What if the
driver property isn't specified ? (that is, is there a default on all iSeries
systems or is that also configurable). In the worst case, the plugin
could be modified to catch an exception for "." and try "/" instead -
though that is kind of ugly.
Rob
On Wed, May 27, 2009 at 3:30 PM, <Chr...@sh...> wrote:
>
> Hello Robert,
>
> I've just discovered squirrel sql and the db2 driver you've written... I
> really want to use this tool and move away from the green screen tools that
> are in use at my company. I'm having trouble though -- it seems that the
> folks around here are using "system" naming instead of "sql" naming. I
> found this article on the web:
>
> http://markmail.org/message/il4lnmefesp7uhqv#query:squirrel%20sql%20system%20naming+page:1+mid:xn3sy4ogdjnkv7st+state:results
>
> Where you apparently were talking to another guy about the same thing. I
> was wondering -- this was a year ago, has any progress been made? Do you
> have any suggestions that I might try?
>
> Thanks in advance for your help!
>
> Christopher Fury
> Shenandoah Life Insurance Company
>
> ****************************************************************************************
> This message may contain confidential information. If it has been sent to
> you in error,
> please reply to advise the sender of the error and then immediately delete
> this message.
> ****************************************************************************************
>
|
