this is better. i did not realize derby supported changing the encryption key.
https://db.apache.org/derby/docs/10.10/devguide/tdevcsecurenewkeyoverview.html
On 4/15/2015 10:57 AM, Peter Ondruška wrote:
Unless I missed something why not just create backup and then open the backup
copy and change encryption key.
On Wednesday, 15 April 2015, John English <[email protected]
<mailto:[email protected]>> wrote:
I have a DB which is encrypted with one password, and I want to generate an
identical copy of it which will be encrypted using
a different password (so that I can provide copies of the same DB for two
different customers without exposing one customer's
password to the other).
I thought at first I could create the tables from a script and then run lots of
"insert into foo (select * from bar)" queries,
but this won't work unless the auto-generated columns are allocated with
the same sequence numbers so that the foreign key
references will match up. And in some case the keys are not sequential, due
to deletions.
Is there an easy way to do this?
TIA,
--
John English
--
Peter Ondruška
--
email: Mike Matrigali - [email protected]
linkedin: https://www.linkedin.com/in/MikeMatrigali
