Match source when creating repository files.
When checking in a new package from the database, the schema name in references throughout the package is changed to have double quotes around it. Then when a change is made on the file, the entries from the database without the double quotes do not match the entries from source control with the double quotes. It seems that this difference alone isn't enough to show the comparison as different, but when another difference exists, these entries are all flagged as different. To resolve this, the double quotes should not be created in the first place.
Thanks Leigh. We believe this is fixed in the latest beta release, please do advise.
-
Leigh commented
I just created a new repository and checked in a schema using version 1.0.0.548. The objects were all created with with an owner name in mixed case in double quotes. The application seems to be assuming that the schema/owner name is the same as the folder name including case. It would be fine to work like this because then it should even have to ask for a folder name to be associated with the schema, but if it is doing this then it should also not put the name in double quotes.