clair/database
Ales Raszka f326b6f664 Use PotentialNamespace in ancestry
If PotentialNamespace is available for given feature it is used instead
of detector namespace. Detector is empty in such a case.
2019-03-14 17:29:41 +01:00
..
pgsql Use PotentialNamespace in ancestry 2019-03-14 17:29:41 +01:00
ancestry.go database: Split models.go into different files each contains one model 2019-03-12 21:55:26 -04:00
database.go database: make locks SOI & add Extend method 2019-02-28 15:46:31 -05:00
dbutil.go Add test for potential namespace 2019-03-08 09:51:19 +01:00
detector.go clair: Use builder pattern for constructing ancestry 2019-02-26 10:26:49 -05:00
error.go database: Add StorageError type 2019-02-19 16:48:42 -05:00
feature_type.go database: Add feature_type database model 2019-02-19 16:48:42 -05:00
feature.go database: Split models.go into different files each contains one model 2019-03-12 21:55:26 -04:00
layer.go database: Split models.go into different files each contains one model 2019-03-12 21:55:26 -04:00
metadata.go database: Split models.go into different files each contains one model 2019-03-12 21:55:26 -04:00
mock.go database: make locks SOI & add Extend method 2019-02-28 15:46:31 -05:00
namespace_mapping.go database: add mapping for Ubuntu Cosmic (18.10) 2018-10-29 13:42:44 -04:00
namespace.go database: Split models.go into different files each contains one model 2019-03-12 21:55:26 -04:00
notification.go database: Split models.go into different files each contains one model 2019-03-12 21:55:26 -04:00
severity_test.go clair: mv updater clair and mv severity to db 2017-01-22 23:20:56 -05:00
severity.go Datastore: updated for Clair V3, decoupled interfaces and models 2017-08-10 11:22:44 -04:00
testutil.go database: move dbutil and testutil to database from pkg 2018-10-08 12:10:35 -04:00
vulnerability.go database: Split models.go into different files each contains one model 2019-03-12 21:55:26 -04:00