Team coding and losing data

[esko.lakso]

We had a case where one of my team members added a column to a table and data was lost du to merge conflict "VCS version". Please make sure that no data is lost when this happens. This can happen in several different ways, below is an example that reproduces the problem each time for us.

Steps to reproduce.

1. Log in to Team coding and pull from remote

2. CREATE TABLE t_test_example_toad_vcs ( idno NUMBER PRIMARY KEY, firstname VARCHAR2(50) );
   INSERT INTO t_test_example_toad_vcs (idno, firstname) VALUES (1, 'Alice');
   INSERT INTO t_test_example_toad_vcs (idno, firstname) VALUES (2, 'Bob');
   commit;

3. Check in table into Team coding and push to remote

4. Check-out the table again.

5. Add columns to the table using this script
   ALTER TABLE t_test_example_toad_vcs ADD (shoe_size NUMBER(3,1));
   UPDATE t_test_example_toad_vcs SET shoe_size = 9.5 WHERE idno = 1;
   UPDATE t_test_example_toad_vcs SET shoe_size = 8.0 WHERE idno = 2;
   commit;

6. Undo the check out
   

   

7. check out the table again

8. Merge warning is shown
   

   

9. select Open VCS version

10. A prompt asking if you want to recompile the table is shown. Selecting yes will recompile the table and this will cause all data in it to be removed. The problem is that there is no warning that data will be lost.
    

    

[esko.lakso]

I have seen that you have updated this in the beta and my Team has tested it.
It is much better that before, but I think it might be even clearer, as I think some junior developers might not understand what a dropped table will result in.

Suggested updated warning:
Table XX will be dropped and recreated using the current VCS version.
All data in table will be lost!
Are you sure?

[JohnDorlon]

Hi Esko,

Sure, we'll add that.

-John