Source control working folder structure
Posted: Thu 01 Feb 2018 04:57
I am evaluating dbForge for SQL server.
When I add a new database object (say, a stored procedure) and commit, it ends up in a sub folder of my working folder called "Programmability\Procedures", which is not the same location that other source control tools, which are still in use, place files.
Is there a way to customise the subfolders where objects of each type go by default?
When I add a new database object (say, a stored procedure) and commit, it ends up in a sub folder of my working folder called "Programmability\Procedures", which is not the same location that other source control tools, which are still in use, place files.
Is there a way to customise the subfolders where objects of each type go by default?