1. René Ullrich
  2. PowerBuilder
  3. Wednesday, 17 October 2018 12:45 PM UTC

Hello,

 

Oracle 12 supports identity columns with new GENERATED AS IDENTITY clause.

I've tried to get it work with PowerBuilder Datawindows (using ORA driver). I specified the identity columns in the datawindow update properties dialog. But I can't get it to work. PowerBuilder doesn't gets the generated value from oracle.

 

Does Powerbuilder supports identity columns with Oracle?

 

mike S Accepted Answer Pending Moderation
  1. Wednesday, 29 June 2022 16:45 PM UTC
  2. PowerBuilder
  3. # 1

funny - MS sql server finally added sequences to match oracle around version 12.   I've always thought sequences a much better implementation.

 

Comment
There are no comments made yet.
Konstantin Goldobin Accepted Answer Pending Moderation
  1. Wednesday, 29 June 2022 14:43 PM UTC
  2. PowerBuilder
  3. # 2

Hello Chris,

I checked this in 2019 R3 and there seems no change in the ORA interface. I was wondering if there are plans to finally "tweak" the driver as you put it?

Best regards,
Konstantin

Comment
  1. Chris Pollach @Appeon
  2. Wednesday, 29 June 2022 15:58 PM UTC
Hi Konstantin .. There were O19C driver "tweaks" in PB2021 & 2022.

Please feel free to test with these releases. The PB2022 Beta is located here: https://www.appeon.com/developers/pb2022-beta.html

If the above newer PB releases do not address your "Identity" column issue, please open a Support Ticket ad attach a test case with details how to recreate the problem. Thanks!

Regards .. Chris
  1. Helpful
  1. René Ullrich
  2. Thursday, 30 June 2022 06:06 AM UTC
There is always a support ticket I created in 2018: https://www.appeon.com/standardsupport/search/view?id=1780

I tested it again with PB 2022 Beta with no success.
  1. Helpful 1
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 17 October 2018 13:16 PM UTC
  2. PowerBuilder
  3. # 3

Hi René;

  Since this is new to Oracle vs being a long time feature of ASE and SS, I suspect that the ORA driver needs to be "tweaked". Normally in ASE or SS when the DWO recognizes an Identity Column (aka Auto Increment) it issues a "ReSelectRow" command behind the scenes to get the new auto assigned value by the DBMS.

  The bad news is that we probably need to open a Support Ticket for this new O12c feature to be supported. The good news is that your App's can use the ReSelectRow() command today (as a workaround) as that command has been a feature in PB for decades.

HTH

Regards ... Chris

Comment
  1. René Ullrich
  2. Wednesday, 17 October 2018 13:24 PM UTC
Hi Chris,



I have not tried it but I guess ReSelectRow would not work. PB can't create the where clause to find the row because it doesn't know the values of the primary key column.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 17 October 2018 14:33 PM UTC
Correct .. so set the Update properties to Identity = None. Then use the ReSelectRow.approach
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


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