Recent content by Brian Baker

With our team's process, we label both the application source code and the database source code with each new build. Then, when I want to update our production environment, I use our source control tool (VSS) to extract the scripts for all the code that has changed since whatever build is...

Great, thanks!

Marco, Although the latest version (I have 6.0.5.926) is supposed to fix this, it does not. When I perform a table import, the following command is executed: C:\oracle\ora81\bin\IMP.EXE log=C:\DOCUME~1\BBAKER\LOCALS~1\Temp\plsimp.log file=C:\EXPAPR20.1043.DMP...

Thanks Marco, I'll give this a shot.

Here is some of the info I gave to my developers: The following PLSQL Developer preferences (Tools | Preferences) are required for proper collaboration in our environment:

Sounds good, Marco. Thanks.

I am using the following versions: PLSQL Dev: 6.0.3.893 VCS Plugin: 1.2.0 VCS System: SourceOffSite Collab 1.1.2 I have the VCS preference "Allow version control over DB objects" enabled. Two problems: 1. If I right-click a package body in the browser and select "Differences", I get a diff...

Not being an Oracle pro, I'm not familiar with "instead of" triggers. Can you expound on your idea a little bit?

I have a table that contains several thousands of records. Is it possible to use the data generator to replace data in a few columns of this table, while leaving the rest of the data (ie, primary key) intact? This would be things like FirstName, LastName, etc., which I see the Data Generator...

In this case we are also using the VCS Preference "Allow version control over DB objects", so a local file may not even be created. If the file does previously exist in the working folder, it remains read-only.

We have the preference "Allow compilation of read-only source files" disabled. If I open a package spec & body and then attempt to check-out, I will be able to edit and compile the package even if the check-out fails. In this case it is because the file is pinned in Visual SourceSafe. I would...

Hmm, didn't know that. Any particular reason? I'm no Oracle expert... all I know is that our client sends us an export file for me to import and I have to do it as sysdba instead of the user. SYS was the first user that worked, so I've stuck with that. ;)

It does not appear that the Import tables procedure (the one that utilizes imp.exe) is working correctly when you are connected as sysdba. Instead of proceeding with the import, I see this in the command prompt window: IMP-00058: ORACLE error 28009 encountered ORA-28009: connection to sys...

Thanks Marco. For the others -- I am trying to build a view to replace a table inside of an Access database. The people that designed that table didn't mind using non-standard characters. ;)

If a column name contains spaces or other special characters (such as a slash), the Query Builder has two problems: 1. The generated SQL does not put quotes around the column name and does not use the correct capitalization that is required when using quoted column names. 2. The "X" does not...