Did you try to decode an encoded file before it was put in the database? If that works, then your database somehow alters the file between storage and retrieval. If that doesn't work then there is probably something wrong with the encoding.
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics
| [reply] |
Thanks for your reply, i want to add one more point here.
When we try to view that file using a Java script in UI it is opening properly, only problem is when we download that file using a PERL script to our local path it's not opening.
Any idea for this issue?
Regards,
Anil
| [reply] |
What has your investigation of the data itself told you? When you load the data into your Perl script and output it from there, for example to a file, and you open that file both in an editor and you produce a hex dump of that file, does it look correct, like base64 encoded data? When you compare a dump of a file that works with a file that doesn't work, what differences do you see?
| [reply] |
