1. Daniel Vivier
  2. PowerBuilder
  3. Wednesday, 9 August 2017 17:10 PM UTC

I'm reading the "Supported Features for Appeon Web" document and it says that bytea is an unsupported data type. We use that to store images in our application. Would there be a work-around for that, other than choosing a different DB? I had somehow not observed that when I decided to try porting our app to Postgres prior to trying a demo of Appeon Web.

I suppose we could use text (text blob) and do some sort of encoding and decoding to and from a text format for the storage of the images, but obviously that would be a bit of a pain. Is there some known standard PB code for doing that sort of encoding/decoding?

Mike S Accepted Answer Pending Moderation
  1. Wednesday, 9 August 2017 18:10 PM UTC
  2. PowerBuilder
  3. # 1

My understanding is that support for bytea was added in build 1102 as per an appeon support email notifying me that my CR/bug was finished/done:

Appeon 2016 build 1102 had support bytea type, please give a try.

I have not tried out the change to see if it works since i have additional postgre items that i need to have supported for my app to work.

  1. Daniel Vivier
  2. Wednesday, 9 August 2017 18:19 PM UTC
Mike, since I'm considering Postgres for my DB for Appeon Web (and have already largely completed adapting one of my apps to use it instead of Firebird SQL) I'd very much like to hear what you are concerned about with this. Perhaps we could do this offline - email me at info@software4nonprofits.com. Thanks!

  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.