Pair of requests to the wishlist

[jcpsaravia]

1. I know that Postgres is case sensitive, but is it possible for the tool to specify PostgreSQL to maintain the lower-upper case present in the gonymizer configuration file when creating the database in which the data will be loaded.

2. Could you add a flag/mechanism in the gonymizer config file so that the pg_dump command does not specify the schema flag? I had cases in which extensions are not being dumped in the backup file and this is because how the schema flag works

[junkert]

I'll try to get to this task this week.

1. Just need to verify I understand this one correctly. Are you saying that the database name that is given to Gonymizer in the Gonymizer config is always lowercased for the "load" operation? Guessing this:

Incorrect:

"database": "MyCamelCase"  => mycamelcase

Correct:

"database": "MyCamelCase" => MyCamelCase

2. The function issue above is an interesting one considering pg_dump documentation is sorely lacking on how it includes functions at the schema level. This will take some research and digging into the documentation to figure it out, but this is an area that needs improved in Gonymizer. More than likely we are implementing this incorrectly.

Thanks for submitting this bug report @jcpsaravia

[jcpsaravia]

With regards to your doubts:

1. Yes you are correct. The issue lies in the fact that if the database (where the anonymized data is to be loaded) is written with capital letters in the configuration file, it is created with lower case letters by PostgreSQL.

2. I just found a work around for this case(not an elegant solution). I basically commented line 71 of the generator.go file.