I have been able to integrate PL/SQL Developer with TFS by installing MSCCI provider and VCS plug-in. However, I have run into a minor issue. Here is description of my issue:
I am dealing with three schemas which has procedures/functions etc. However, some procedure names are not unique across database. For example, schema_a has a.prc and schema_b has a.prc. Unfortunally, I can not store SRC for all schemas in one directory of TFS (these two will overwrite). PL/SQL recognizes/detects if an object is under source control by looking at the file name and expecting them to be procedure_name + extension [No provision for schema ].
Is there any workaround for this? Any setup/preference option in PL/SQL which will allow me to use schema_name as prefix potentially and it still be recognized as VCS plug-in.
I have an ugly work-around i.e. I will need to store code for schema in seperate directory of TFS. However, it brings another issue i.e. I will have to have "multiple VCS projects -- mapping to different directory).
I would like to simplfy the process so developers get into habit of checking-in code from PL/SQL Developer without too much of hassle.
Thx!
I am dealing with three schemas which has procedures/functions etc. However, some procedure names are not unique across database. For example, schema_a has a.prc and schema_b has a.prc. Unfortunally, I can not store SRC for all schemas in one directory of TFS (these two will overwrite). PL/SQL recognizes/detects if an object is under source control by looking at the file name and expecting them to be procedure_name + extension [No provision for schema ].
Is there any workaround for this? Any setup/preference option in PL/SQL which will allow me to use schema_name as prefix potentially and it still be recognized as VCS plug-in.
I have an ugly work-around i.e. I will need to store code for schema in seperate directory of TFS. However, it brings another issue i.e. I will have to have "multiple VCS projects -- mapping to different directory).
I would like to simplfy the process so developers get into habit of checking-in code from PL/SQL Developer without too much of hassle.
Thx!
