Wang Yan add8dedc90 Fix the database upgrade issue (#11766) ... It's a workaround for issue https://github.com/goharbor/harbor/issues/11754 The phenomenon is the repository data is gone, but artifacts belong to the repository are still there. To resolve it, just set the repository_id to a negative, and cannot duplicate. Signed-off-by: wang yan <wangyan@vmware.com>		2020-04-27 17:28:36 +08:00
..
0001_initial_schema.up.sql	Set default email to null if not provided	2019-08-19 15:20:44 +08:00
0002_1.7.0_schema.up.sql	Update the upgrade sql to rename the duplicate records	2019-01-04 14:55:33 +08:00
0003_add_replication_op_uuid.up.sql	Add op uuid to image replication	2018-10-21 23:55:57 +08:00
0004_1.8.0_schema.up.sql	Fix migrator scan all schedule from v1.7.0 (#7763)	2019-05-10 17:08:52 +08:00
0005_1.8.2_schema.up.sql	Delete the nono scan all schedule in migration	2019-08-01 16:59:13 +08:00
0010_1.9.0_schema.up.sql	Move db change to new migration file	2019-09-25 15:57:03 +08:00
0011_1.9.1_schema.up.sql	Move db change to new migration file	2019-09-25 15:57:03 +08:00
0012_1.9.4_schema.up.sql	Support pinning to authproxy server's cert	2019-12-03 07:31:26 +08:00
0015_1.10.0_schema.up.sql	Avoid to create duplicated immutable tag rules in the same project	2019-11-15 14:46:23 +08:00
0030_2.0.0_schema.up.sql	Fix the database upgrade issue (#11766)	2020-04-27 17:28:36 +08:00