1. Konstantin Goldobin
  2. PowerBuilder
  3. Tuesday, 17 September 2019

Hello,

I was wondering if anyone knows how to stop PowerBuilder from qualifying an Oracle procedure with its owner in DataWindow Stored Procedure Update properties. We are using a native Oracle driver, not ODBC.

Best regards,
Konstantin

Miguel Leeuwe Accepted Answer Pending Moderation
0
Votes
Undo

I posted it as a request (bug 3362) and sofar this it what Chris has answered me. I'll try to do that tomorrow, though maybe not for everyone it's easy to get dbo rights on his assigned Oracle user.

 

Hi Miquel;

  I believe that the DBO (DB Owner) is added to the DWO's SQL statement when the PB Developer's DBMS login ID is not assigned the DBO role. I have seen this in ASE and SQL Server. By adding the DBO role in those DBMS for me, has always then allowed the PB IDE to drop the prefix.

  Have you tried this in Oracle?

Regards ... Chris


Comment
Thanks, Miguel! I believe DBO is a Sybase/SQL Server artefact but I wouldn't know its counterpart in Oracle... Do you?
  1. Konstantin Goldobin
  2. Thursday, 19 September 2019
I've tried to assign SYS and SYSDBA to my user and then specify SYSDBA for "Connect as".

It doesn't make a difference.

I've also noted that once you've created the dw, there's no way to "change the datasource". The icon and the menu option is disabled.
  1. Miguel Leeuwe
  2. Thursday, 19 September 2019
There are no comments made yet.
  1. Wednesday, 18 September 2019
  2. PowerBuilder
  3. # 1
Miguel Leeuwe Accepted Answer Pending Moderation
0
Votes
Undo

I guess the best thing to do here, is to ask for an improvement / feature request / enhancement to Appeon to achieve the goal of NOT having to edit the dw source code manually all the time.

I'll do that right now.

 

Comment
There are no comments made yet.
  1. Wednesday, 18 September 2019
  2. PowerBuilder
  3. # 2
Juan Alejandro Lam López Accepted Answer Pending Moderation
0
Votes
Undo

Respect to PB does not list synonyms for procedures/packages in the selection list..., please verify the file adjunct.

Attachments (1)
Comment
(sorry should have sent that in English)
  1. Miguel Leeuwe
  2. Wednesday, 18 September 2019
Lo que quiero decir es que si se listan los sinonimos, las imagenes que ves son para que compruebes como se hace.
  1. Juan Alejandro Lam López
  2. Wednesday, 18 September 2019
Hi Juan! Not sure I see your point. If I understand correctly your example, you have a synonym for sys.utl_listar in the LAM schema, and when you select one of its procedures PB qualifies it with the synonym owner LAM, which is exactly what I want to avoid...
  1. Konstantin Goldobin
  2. Thursday, 19 September 2019
There are no comments made yet.
  1. Wednesday, 18 September 2019
  2. PowerBuilder
  3. # 3
Miguel Leeuwe Accepted Answer Pending Moderation
0
Votes
Undo

In the PB IDE, in the connection profile, do you have the powerbuilder catalog owner set to the schema who owns the stored procedure? Do you have synonyms?

Sorry cannot test now myself, as our servers are being maintained.

If not ... do what Juan Alejandro says, though that's something you might have to repeat every time you change something on the dw.

Comment
Yes to both questions - and that's why I don't understand why PB insists on qualifying procedure calls with their owner. BTW, surprisingly enough, PB does not list synonyms for procedures/packages in the selection list...
  1. Konstantin Goldobin
  2. Wednesday, 18 September 2019
Yes, I've tested it on our system too. I think this goes back to the days when Oracle was a big competitor of Sybase System 10, ASE, etc. In the early years Powersoft and Sybase were "most compatible" (in favour) and fully supported Sybase, but not so much the competitors. This has been like this since the nineties if I remember well.
  1. Miguel Leeuwe
  2. Wednesday, 18 September 2019
There are no comments made yet.
  1. Tuesday, 17 September 2019
  2. PowerBuilder
  3. # 4
Juan Alejandro Lam López Accepted Answer Pending Moderation
1
Votes
Undo

The method that I use, is to edit the Datawindow, by right clicking on the datawindow and selecting the Edit Source option. Then remove the Owner from the Invocation of the Stored Procedure.

Comment
Thanks! This is what we've been doing as well but this is ridiculous, don't you think?
  1. Konstantin Goldobin
  2. Wednesday, 18 September 2019
There are no comments made yet.
  1. Tuesday, 17 September 2019
  2. PowerBuilder
  3. # 5
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.