How can we help you today? How can we help you today?
Brian.Lieb
Activity overview Badges (0) Posts (10) Comments (10)

Comments

Sort by recent activity
Update: Thanks for your input. I will definitely keep this in mind for next time. The fix with some background. As you can probably tell from the above two messages, this database was a development database that I was making changes to before committing to the repository. As I mentioned, Source Control saw a difference between the source database and the repository. After the initial commit, no matter how many more times I committed that change, I kept getting the error "Nothing to commit" even though the Oracle Source Control kept showing there was something to commit. So, after reading your message, I realized that I had not used Schema Compare directly, so I checked the repository out to my hard drive using TortoiseSVN. I then compared the Scripts folder that was made from the checkout to my development database, where it found a difference (again, the diff screen showed no differences). I deployed that change from schema compare, it dropped and recreated a unique index (with the exact same name and columns). After the deploy, Schema Compare showed there were no differences between the scripts folder and the database. I refreshed Oracle Source Control, and it too saw nothing to commit. Thanks. / comments
  1. Community
  2. Source Control for Oracle
  3. Committing issues
Update: Thanks for your input. I will definitely keep this in mind for next time.The fix with some background. As you can probably tell from the above two messages, this database was a developmen...
0 votes
Follow up: I removed the offending table from the repository using TortoiseSVN. When I launched Source Control for Oracle, it noticed. I chose the Database Version as the correct version to commit. I committed it. === The Project still shows one difference, but not the diff, and I cannot commit again. / comments
  1. Community
  2. Source Control for Oracle
  3. Committing issues
Follow up: I removed the offending table from the repository using TortoiseSVN. When I launched Source Control for Oracle, it noticed. I chose the Database Version as the correct version to commit...
0 votes
Hi, Thanks for the response. I have done this, and things seemed to be working fine for checking out, and then comparing using schema compare. To be clear the steps I took were - Checked the repository using Tortoise to two places on my harddrive. (repo1, repo2) - Used schema compare to 'Update' repo1, which removed the .svn folder and thereby removing the recognition this is an SVN repo from Tortoise - Copied the contents of repo1 over the top of repo2, making sure to overwrite the files in repo2. - Checked in repo2. - Removed all local copies. - Used Tortoise to checkout again to a folder called repo - Opened Schema compare and used the repo as the source VOILA! I don't need to update any more and schema compare works fine. However, now, when I try to check in changes via Oracle Source Control, I get this error: Error Some objects were out of date. Review the changes and check in again. Report When I click the Report link, Source Control crashes with this: System.NullReferenceException: Object reference not set to an instance of an object. at Smartassembly.SmartExceptionsCore.UnhandledExceptionHandler.ReportException(Exception exception, Boolean, continue, Boolean manuallyReported) I can probably destroy the entire repository and start over from the schema, but that is not a palatable option. Is there any suggestion on how to proceed? / comments
  1. Community
  2. Schema Compare for Oracle
  3. Schema Compare/Source Control
Hi, Thanks for the response. I have done this, and things seemed to be working fine for checking out, and then comparing using schema compare. To be clear the steps I took were - Checked the repos...
0 votes
Followup: I removed the project from Oracle Source Control, and re-created it and was able to check the project in without an error. Unfortunately, this did not fix the problem for all the other users. This is not 'unfixable', but is not very convenient or easy to fix. I have seen this error before in other SVN clients, and I was able re-checkout the repo to fix it. It seems like something must be out of synch on the local machine. / comments
  1. Community
  2. Schema Compare for Oracle
  3. Schema Compare/Source Control
Followup: I removed the project from Oracle Source Control, and re-created it and was able to check the project in without an error. Unfortunately, this did not fix the problem for all the other us...
0 votes
Sheesh! I am an idiot. This has been going on awhile, and in the interim a new version of both Schema Compare and Source Control have been released. This issue no longer seems to be one, I apologize for wasting your time. / comments
  1. Community
  2. Source Control for Oracle
  3. More issues with comments on views
Sheesh! I am an idiot. This has been going on awhile, and in the interim a new version of both Schema Compare and Source Control have been released. This issue no longer seems to be one, I apolog...
0 votes
Source Control: 2.0.2.404 Schema Compare: 3.0.2.348 / comments
  1. Community
  2. Source Control for Oracle
  3. More issues with comments on views
Source Control: 2.0.2.404 Schema Compare: 3.0.2.348
0 votes
I voted for public synonym support. As for the link about synonyms, it doesn't really help to hear about how public synonyms are bad practice. I work on a large system that was developed 10-15 years ago, and synonyms play a large role, including thousands of lines of pl/sql. Dropping synonyms is not a simple undertaking, and without an easy way to track changes via source control, it is made more difficult. / comments
  1. Community
  2. Schema Compare for Oracle
  3. Public Synonyms
I voted for public synonym support. As for the link about synonyms, it doesn't really help to hear about how public synonyms are bad practice. I work on a large system that was developed 10-15 year...
0 votes
I don't want to harp on this too much, as I am a developer and know all too well the pain of being asked, "When will that be fixed?" However, we would really like to begin using Source Control for Oracle, and the schema is way too large to go through and change all the comments. (Plus, we shouldn't have to.) So, I guess, you have given me what appears to be a JIRA issue number, but no way to track it, so I am wondering if this fix will be in a release soon or not? / comments
  1. Community
  2. Source Control for Oracle
  3. Error when refreshing (Comment has a single quote in it)
I don't want to harp on this too much, as I am a developer and know all too well the pain of being asked, "When will that be fixed?" However, we would really like to begin using Source Control for ...
0 votes
Okay. In my frustration, I have made two blank schemas. In the first, I put a table with two columns. CREATE TABLE mytable (col1 VARCHAR2(5 BYTE), col2 VARCHAR2(5 BYTE)) ; COMMENT ON TABLE mytable IS 'This is mytable''s awesome data.'; COMMENT ON COLUMN mytable.col1 IS 'Column 1''s values are stored here'; COMMENT ON COLUMN mytable.col2 IS 'Column 2'; Then I made this view: CREATE OR REPLACE VIEW myview ( col1, col2 ) AS select col1, col2 from mytable; COMMENT ON TABLE myview IS 'This view shows mytable''s data.'; COMMENT ON COLUMN myview.col1 IS 'Column 1''s value from the view'; COMMENT ON COLUMN myview.col2 IS 'Column 2 value from the view'; That is the exact SQL I ran to create the views and tables. It worked fine. Then I did a schema compare between the schema with the new table and view against the blank schema. And chose to to a deployment to a script. The script that was generated was this: -- -- Script generated by Schema Compare for Oracle 3.0.0.790 on 12/10/2013 11:45:49 AM -- SET DEFINE OFF CREATE TABLE schema2.mytable ( col1 VARCHAR2(5 BYTE), col2 VARCHAR2(5 BYTE) ); COMMENT ON TABLE schema2.mytable IS 'This is mytable''s awesome data.'; COMMENT ON COLUMN schema2.mytable.col1 IS 'Column 1''s values are stored here'; COMMENT ON COLUMN schema2.mytable.col2 IS 'Column 2'; CREATE FORCE VIEW schema2.myview (col1,col2) AS select col1, col2 from mytable; COMMENT ON TABLE schema2.myview IS 'This view shows mytable's data.'; COMMENT ON COLUMN schema2.myview.col1 IS 'Column 1''s value from the view'; COMMENT ON COLUMN schema2.myview.col2 IS 'Column 2 value from the view'; So, you can see that the comment on the view is wrong! So, as one last check, I ran this: select dbms_metadata.get_dependent_ddl('COMMENT', 'MYVIEW', 'SCHEMA1') from dual To see what Oracle returned. The results: COMMENT ON COLUMN "SCHEMA1"."MYVIEW"."COL1" IS 'Column 1''s value from the view' COMMENT ON COLUMN "SCHEMA1"."MYVIEW"."COL2" IS 'Column 2 value from the view' COMMENT ON TABLE "SCHEMA1"."MYVIEW" IS 'This view shows mytable''s data.' As you can see, Oracle is returning it correctly as well. So, I have surmised that either I am missing something really small, or there is a bug in generating comments in Red Gate's schema compare when looking at views. / comments
  1. Community
  2. Source Control for Oracle
  3. Error when refreshing (Comment has a single quote in it)
Okay. In my frustration, I have made two blank schemas. In the first, I put a table with two columns.CREATE TABLE mytable (col1 VARCHAR2(5 BYTE), col...
0 votes
I'm sorry, I don't have any idea what version of oracle these comments were made on. Anyway, I used Tortoise to get the scripts and the comments field that is causing the problem looks like this: COMMENT ON TABLE myview IS 'The coop's name and some additional calculated columns.'; Seems obvious why there is a problem. What is interesting is this: COMMENT ON COLUMN myview.mycol IS 'Amount of this year''s payment that has covered accrued interest'; Is a comment on a column in the same view. It has the '' so it is fine. Finally, there is one more piece of information. I am unable to find a comment definition for any view that contains a ' that is properly escaped. However, the comment definitions on the tables that have a ' are all escaped correctly. COMMENT ON TABLE myTable IS 'Table captures hard copy User''s Comment Form'; I will look into schema comparing to a blank schema, and making the repo from there also, but I thought you might be interested in the info I have found. / comments
  1. Community
  2. Source Control for Oracle
  3. Error when refreshing (Comment has a single quote in it)
I'm sorry, I don't have any idea what version of oracle these comments were made on. Anyway, I used Tortoise to get the scripts and the comments field that is causing the problem looks like this:CO...
0 votes
Total activity
25
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
5