1. Brian Prom
  2. PowerBuilder
  3. Monday, 16 October 2017

Any issues with BLOB or CLOB columns?

Thanks,
Brian Prom

Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Brian;

      Yes, PB 2017 supports the SS interaction using ODBC amongst other DB client drivers as well. For BLOB (or CLOB) columns the key here (because of their large size), is to either change the PBnnnODBC.ini file or add the "PBMaxBlobSize" and "PBMaxTextSize" to the DBParm field of your SQLCA transaction object, as follows (for example):

  • SQLCA.DBParm="PBMaxBlobSize=2000000"
  • SQLCA.DBParm="PBMaxTextSize='98000'

  With the above settings in the INI file or in your SQLCA.DBparm and the appropriate maximum values are set, the BLOB & CLOB handling through ODBC should be as easy as using the SS native driver that Marco mentions. Note that without these above settings, the ODBC driver will default to 32K each Max.

HTH

Regards ... Chris

Comment
There are no comments made yet.
  1. Tuesday, 17 October 2017
  2. PowerBuilder
  3. # 1
Marco Meoni Accepted Answer Pending Moderation
0
Votes
Undo

Hello,

PB advises to use native drivers. From PB 2017 help: "You can access Microsoft SQL Server 2008 R2, 2012, 2014 or 2016 databases using the SQL Native Client interface".

As far as your specific question on the 2 datatypes, MS SQL Server rather uses VARCHAR and NVARCHAR to store variable-length character data up to 2 GB.

At any rather, CLOB and BLOB (Oracle, DB2, IQ) datatypes are fully supported by PB 2017.

Appeon also supports them, but they can only be used in SELECTBLOB and UPDATEBLOB SQL statements.

Cheers,

Marco

Comment
There are no comments made yet.
  1. Tuesday, 17 October 2017
  2. PowerBuilder
  3. # 2
  • Page :
  • 1


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