Would the version bump be a good time to fix the "UNICODE" encoding misnomer in database creation and in the backend param status? I assume it should be "UTFx".