Fix issue #228
Function sqlite3mc_cipher_name is not thread-safe. This could cause runtime errors, if several threads try to open a database connection at the same time. - The internal implementation has been changed to avoid calling sqlite3mc_cipher_name - API function sqlite3mc_cipher_name_copy has been added, which is thread-safe
U
utelle committed
07a1a60ce6439467620e247c88e0449572e03cb5
Parent: 158d582