plsqldeveloper vcs/browser questions

[ora1001]

Hi,

1)
Is there a way i can create a new folder using the object browser folder of Type .sql? basically all files under that folder will have .sql files... so that we can add those as well to our version control system..

2)
Example: We have package1. user1 checkedout package1 and user2 copied the same package to a sql window change something and compiled it. So now database has user2 version. Now when user1 is done with his changes and he compiles again the database version gets replaced. Is there a way in plsql developers to restrict this kind of scenarios atleast for packages, functions? so that these files will be considered as static and will help do check-in/checkout with out any confusions?

Any other alternative also,would help us...

Thanks in advance

 

[Marco Kalter]

I'm not sure I understand. Object Browser Folders do not deal with files or extensions, but only with objects in the database. Perhaps you can elaborate?

 

[ora1001]

1)
For example:
Procedures Folder will have procedures with extension .prc
Functions Folder will have procedures with extension .fnc
Similalry is there a way
SQLScripts Folder will have procedures with extension .sql

2) please let me know, if any idea on question 2 as well.

 

[Marco Kalter]

Are you talking about the File Browser or the Object Browser?

 

[ora1001]

am talking about object browser.

 

[Marco Kalter]

But the Object Browser does not deal with files, so file concepts like extensions do not apply...

 

[ora1001]

thank you.. what about question 2

2)
Example: We have package1. user1 checkedout package1 and user2 copied the same package to a sql window change something and compiled it. So now database has user2 version. Now when user1 is done with his changes and he compiles again the database version gets replaced. Is there a way in plsql developers to restrict this kind of scenarios atleast for packages, functions? so that these files will be considered as static and will help do check-in/checkout with out any confusions?

 

[Marco Kalter]

You would have to use a version control system. This way the package source will have to be checked out before it can be edited, and will be read-only for other users. If you additionally disable the "Allow compilation of read-only files" preference, you can ensure that the database version always matches the latest working version.