ok folks, sorry to bother you all with this... i figured out what to do. you have to use a char for bit data column -- NOT a varchar for bit data column. in case this happens to anyone else, some other notes:
if your data varies in size, when you insert your binary data DB2 will append filler crud to it (CHR 32). slightly annoying but easy to strip. my data doesn't, so i am just using a char col of the proper size and now i can happily read and write my binary data. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] > Sent: Wednesday, January 15, 2003 5:46 PM > To: [EMAIL PROTECTED] > Subject: RE: [DB2EUG] storing encrypted data > > > > > > > > Steve Shapero writes: > >i set my column to be varchar for bit data, but my encrypted data is > >still > getting munged. > > You don't have to store binary data. You could simply change > your program to UUENCODE the data to text before inserting it > into the table. Other binary-to-ASCII encoding algorithms > would work as well. > > Good Luck, > > Fred > > > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] > *** For more information, check http://www.db2eug.uni.cc > - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
