Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2005-12-20T17:44:04Z by SystemAdmin
SystemAdmin
SystemAdmin
2826 Posts
ACCEPTED ANSWER

Pinned topic Force Translate in Connection String?

‏2005-12-20T04:57:13Z |
Hi,

I only had just figured out a hack to get the .NET v1 provider to translate CCSID 65535 binary fields to text, and now I'm a bit lost again.

Is there a connection string setting, or some static property I can set to tell the provider that AS400/DB2 binary fields are text?

Thanks!

James
Updated on 2005-12-20T17:44:04Z at 2005-12-20T17:44:04Z by SystemAdmin
  • bpgross
    bpgross
    627 Posts
    ACCEPTED ANSWER

    Re: Force Translate in Connection String?

    ‏2005-12-20T05:56:46Z  in response to SystemAdmin
    There is no force translate or similar option in the DB2 .NET data provider. I am aware of this requirement, but unfortunately we do not have a solution at this time.

    Brent.
    • SystemAdmin
      SystemAdmin
      2826 Posts
      ACCEPTED ANSWER

      Re: Force Translate in Connection String?

      ‏2005-12-20T17:44:04Z  in response to bpgross
      Aww, that's a shame. I got so excited when I found it hiding in the v1.1 provider (had no public setter, but reflection did the trick).

      Anyhoo, ok, maybe even better than that would be a DB2 SQL function that converted binary text (65535) to plain old Windows text (37). I can do this after it is returned to the client, but it would be much cleaner to do it in the stored procedures.