August 23, 2005 at 4:51 am
We're using the WITH ENCRYPTION option on some of our more sensative stored procedures. We have noticed occasionally a carriage retur is lost, which ends up concatenating 2 lines together creating a syntax error at run time.
We have not confirmed 100% that this is related to the encryption, but I was wondering if anyone else has experienced this?
Thanks!
August 23, 2005 at 8:02 am
If you make an unencrypted version (I mean EXACT COPY/PASTE). Does it work or does it still have the problem?
August 23, 2005 at 8:15 am
It does still have the problem. It may be something in how the script is executed rather than the encryption. It appears to be removing the CR (char 13) but leaving the LF (char 10) but the net result is the lines get concatenated.
August 23, 2005 at 9:16 am
Do you have comments around that line? I know there is a little interpretation bug when that happens.
August 23, 2005 at 11:42 am
Actually, there are. I've heard something like that before. There are some double dash -- comments near by. Is there a workaround or any documentation on this?
Thanks very much for the info!
August 23, 2005 at 11:45 am
I don't remember the actual exact reason for this, but what happens is that the crlf gets cut on 2 separate lines so it stops working. Add a few characters to the comments, then reinsert the return and apply the changes... you should be fine then.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply