8fd0aa162b
various: spelling corrections
9 years ago
84319507df
database: use constants to store queries
9 years ago
06531e01c5
database: disable hash/merge joins in FindLayer
...
Our experiments have shown that PostgreSQL 9.4 makes bad
planning decisions about:
- joining the layer tree to feature versions and feature
- joining the feature versions to affected/fixed feature version and vulnerabilities
It would for instance do a merge join between affected feature versions (300 rows, estimated
3000 rows) and fixed in feature version (100k rows). In this case, it is much more
preferred to use a nested loop.
9 years ago
6d2eedf121
api/database: add the layer name that add each feature in getLayer
9 years ago
f0816d2c4d
database: add docs about the interface
9 years ago
d3b14106a9
database: ignore insertLayer collisions to make it truly idempotent
9 years ago
5fdd9d1a07
*: add metadata support along with NVD CVSS
9 years ago
baed60e19b
prometheus: add initial Prometheus support
9 years ago
563b3825d8
database: let handleErrors deal with the not found case
9 years ago
726bd3c0c6
database/api: add layer deletion support
9 years ago
82175dcfe9
*: add missing copyright headers
9 years ago
92b734d0a4
database: remove an useless query in FindLayer
9 years ago
7c70fc1c20
database: add initial vulnerability support
9 years ago
3a786ae020
database: add lock support
9 years ago
6a9cf21fd4
database: log and mask SQL errors
9 years ago
970756cd5a
database: do insert/find layers (with their features and vulnerabilities)
9 years ago
2c150b015e
*: refactor & do initial work towards PostgreSQL implementation
9 years ago
Jimmy Zelinskie