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.
5 years ago
a8a91379d9
Add test for potential namespace
...
Test verifies that potential namespace is stored in database and it can
be loaded back to structure.
The commit also fixes few typos and bugs.
5 years ago
60b0bd27fa
Add namespace_id as constraints to layer_feature
...
If layer contains more than one potential namespace, features will be
created for each namespace. Layer_feature table now has to contains one
more constrains (namespace_id).
5 years ago
44c4a6f3ce
Store PotentialNamespace in database
...
PotentialNamespace is part of layer_feature table and it is also stored
in namespace table.
5 years ago
5bf8365f7b
pgsql: Prevent inserting invalid entry to database
5 years ago
c6c8fce39a
pgsql: Add feature_type to initial schema
...
feature_type is for differentiating the binary packages and source
packages.
5 years ago
0c1b80b2ed
pgsql: Implement database queries for detector relationship
...
* Refactor layer and ancestry
* Add tests
* Fix bugs introduced when the queries were moved
6 years ago
dca2d4e597
pgsql: Add detector to database schema
...
'detector' table is added to store the metadata of detectors.
'layer_feature', 'layer_namespace', and 'ancestry_feature' tables are
modified to store the detection relationship between the
feature/namespace with the detector.
6 years ago
53433090a3
pgsql: update the query format
6 years ago
2827b9342b
Update Database and Worker implementation for layer-wise feature
...
Feature extraction algorithm is changed to associate features with
ancestry layer. Database is updated to keep the relationship.
6 years ago
a5c6400065
database: postgres implementation with tests.
7 years ago
Ales Raszka