Re^2: MySQL AES Encryption with CBC mode

Yes, running two commands as one is apparently the problem, but I'm not certain running them separate terminates the initial assigned "session" and reverts to defaults with the second command.

I'm not 100% sure the difference between "encrypted" and "hashed". My best guess: hashed is one way; and encrypted can be decrypted... so my answer: I currently need the option to decrypt for additional software access (which is not to be tinkered with).

Comment on Re^2: MySQL AES Encryption with CBC mode

Replies are listed 'Best First'.
Re^3: MySQL AES Encryption with CBC mode by haukex (Archbishop) on May 17, 2017 at 06:32 UTC
running them separate terminates the initial assigned "session" and reverts to defaults with the second command. That's part of what I meant when I was talking about calling `DBConnect` every time `DBRun` or `DBDo` gets called: This will establish a new connection to the database for every command you run, so that will certainly cause the session to be ended and a new one begun. Have you tried to see what happens when you connect only once at the beginning of the script and then run your commands separately?	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: MySQL AES Encryption with CBC mode
by haukex (Archbishop) on May 17, 2017 at 06:32 UTC

running them separate terminates the initial assigned "session" and reverts to defaults with the second command.

That's part of what I meant when I was talking about calling DBConnect every time DBRun or DBDo gets called: This will establish a new connection to the database for every command you run, so that will certainly cause the session to be ended and a new one begun. Have you tried to see what happens when you connect only once at the beginning of the script and then run your commands separately?

[reply]
[d/l]
[select]