Bug 6221

PB 2019 Crashes When using SelectBlob with a string argument of about 1000 characters 13 April, 2021

Ankur Patel
05 March, 2021
Product: PowerBuilder Category: Database
Version: 2019 R3 Build: 2670
Classification: Sybase (legacy) bug Publishing: Public
Priority: P2
Status: Scheduling Reason:
Communication Status: Waiting for Customer
Ken Guo @Appeon 09 April, 2021
Appeon Workaround

Hi Ankur,

In order to be familiar with this workaround,I made changes to your previous case, please download and view.

Before use, please execute the SQL statements in SQLQuery1 in order to create related tables and stored procedures.

In addition, pay special attention to: When accepting the return value in the PB, it needs to be consistent with the actual type of the return value in the stored procedure. In the case, I call two stored procedures separately for explanation. 

If you have any questions, please let us know.

Ankur Patel 08 April, 2021
Hello Ken,

I can't seem to make this work. Did you modify the test application or the database procedure in some way? I tried modifying the procedure to use 2 arguments, one for input and another for output but I am not able to get the output. If you have modified the test application or database procedure in some way can you please send me the details?

Ankur Patel
Ken Guo @Appeon 08 April, 2021
Hi Ankur,

Sorry to let you know that we don't have a plan to fix this issue within a short time.
Could you work around this issue by calling SP as follows:

DECLARE sp_crashing_demo_proc PROCEDURE FOR 
   sp_crashing_demo  @as_arg = :ls_arg,  @ls_result=:lbl_temp;
execute sp_crashing_demo_proc;

Ankur Patel 07 April, 2021
Hi Ken,

Is there any progress on this? This seems like a simple string limit issue. 

Ankur Patel
Ken Guo @Appeon 31 March, 2021
Hi Ankur,

There is no progress on this issue at present yet. We will update you here once there is any progress.

Ankur Patel 31 March, 2021
Hello Support Team,

Is there any update on this? We are really facing a lot of issues due to this.

Ankur Patel
Ankur Patel 30 March, 2021

Is there any update on this?

Ankur Patel
Baron Zhang @Appeon 08 March, 2021
Hi Ankur,
Thanks for reporting this problem! we’ve submitted the issue to our development team for further analysis for a solution. 

Ken Guo @Appeon 05 March, 2021
Hi Ankur,

Thanks for reporting this problem! We reproduced it on our end and will do further research to figure it out. We will keep you posted about the progress.

BTW, PB 12.6 has the same issue as well. PB 11.5 works.

Ankur Patel 05 March, 2021
crashing_demo.zip (676KB)

PowerBuilder crashes when using selectblob query with a large string argument. It seems when the overall query length goes beyond 1000 characters, it crashes.

*Reproduce Steps:
I have attached a sample application and a newly created SQL Anywhere 17 database.
Create an ODBC DSN named "crashing_demo" using the provided database.
Run the provided sample application and it will crash.

In the sample application, the open event has the script to connect to the database and open a blank window.
In the open event of the window, there is a simple selectblob query of a stored procedure.
The database is completely blank, it has only one stored procedure called from the PowerBuilder as shown below.

CREATE PROCEDURE "dba"."sp_crashing_demo"(in as_arg varchar(1000))
Result(ls_result varchar(1000))
    Select 'A';

I have selected the priority P2 because this is crashing our application at a lot of places and we haven't found any workaround yet. This issue is not there in PB 11.5.

Ankur Patel
Database Type:
SAP SQL Anywhere
Database Version: