Comments
6 comments
-
I can reproduce this so I'll investigate.
-
Great. Thanks!
-
Unfortunately whilst I reproduced this first time round I'm afraid we can't do so anymore, that is this functionality works properly. Can you provide a full repro?
-
What did you do differently on the subsequent tests? Did you change something in the project configuration?
Here are the things I've tried several times and always got the same result:
- drop and recreate the table
- alter the column to generate an updated script
- delete and recreate the project
I saved the changes in the tool but never committed them to source control because the output script is wrong.
I have attached screenshots of the various project configuration and tool version information.
Update: I am using the 32-bit version of the tool as I have the 32-bit version of Oracle 12c installed locally.
Thanks,
-
Direct support helped me resolve the issue. The problem was caused by an ignore rule on sequences. I erroneously assumed that ignoring the sequences did not impact the identity column. I modified the ignore rule to only pick up sequences that begin with ISEQ to avoid scrolling through 600+ other sequences that have no use to my project.
Thanks for all the help! -
hello,i am new here from india, here to share some thoughts with you all
Add comment
Please sign in to leave a comment.
Table script:
CREATE TABLE REDGATE.SCO_TEST( SCO_TEST_ID NUMBER GENERATED BY DEFAULT AS IDENTITY, PROPERTY_NAME VARCHAR2(20) NOT NULL,
PROPERTY_TYPE VARCHAR2(50) NOT NULL,
PROPERTY_VALUE VARCHAR2(100),);
Script preview from Source Control for Oracle:
CREATE TABLE redgate.sco_test (
sco_test_id NUMBER NOT NULL,
property_name varchar2(20) NOT NULL,
property_type varchar2(50) NOT NULL,
property_value varchar2(100)
);