1. Thomas Rolseth
  2. SnapDevelop
  3. Tuesday, 31 December 2019 14:13 PM UTC

We are using PB/SnapDevelop 2019 build 2082 with an Oracle 12 database.  I created a datawindow/datastore object with a SELECT that matches the columns and datatypes of an external datawindow and then ported it to the API using the C# Model Generator.  Once populated with data in the API, we want to use ShareData() in the client to populate the existing external datawindow. 

One of the columns in the select for the new datastore dw is a LONG data type.  The new datastore retrieves the column just fine in PB.  I can also cut, paste and run the select in the PB database painter and it will return rows.  However, when it is retrieved as part of a service method in the API, the column is blank.  This seems like a .NET datastore bug to me given that the retrieve works ok in PB but not SnapDevelop.  Because the client application does not have any embedded SQL I need to figure out a way in the API to set this column by converting the LONG data into a string.  Any thoughts or suggestions on how best to do that?

Thanks, Tom

Accepted Answer
Thomas Rolseth Accepted Answer Pending Moderation
  1. Friday, 24 January 2020 16:49 PM UTC
  2. SnapDevelop
  3. # Permalink

We resolved this by creating a service method inthe Web API that calls stored procedure.  the procedure uses an Oracle global temporary table to convert the long column to a blob using to_lob().  then we were able to output the value as a string.


  1. Armeen Mazda @Appeon
  2. Friday, 24 January 2020 17:03 PM UTC
Thanks for sharing the solution!
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 31 December 2019 14:52 PM UTC
  2. SnapDevelop
  3. # 1

Hi Tom;

   if no one can provide a reasonable answer to this problem (I cannot off-hand), please report this issue by opening a Support Ticket.

Regards ... Chris

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.