| Commit message (Collapse) | Author | Age |
|
|
|
| |
With local development instructions.
|
|
|
|
| |
I think the .go files should be in lib, rather than share.
|
|
|
|
| |
This is used as a Guile module.
|
|
|
|
| |
This is a generated file.
|
|
|
|
| |
As this is useful when setting custom configuration.
|
|
|
|
| |
The repository id is expected to be a number.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
As this is easier to handle when doing queries with PostgreSQL, as you can use
the type information to determine how to handle the values.
|
|
|
|
|
| |
Represent non-string home pages as NULL, and delete duplicates, as package
metadata entries can be duplicated.
|
| |
|
|
|
|
|
|
| |
This is useful when you want to pass in data with some duplicates, and get
back a list of ids, where the duplicate entries are represented by the same
id.
|
|
|
|
|
|
|
| |
Add tests around the package module, extract out the use of the
inferior-package record assessors so that they aren't part of the tests, and
switch across the package-metadata module to use
insert-missing-data-and-return-all-ids.
|
|
|
|
| |
About mocking the record file accessors not working :(
|
|
|
|
|
|
|
|
|
| |
squee, returns all data as strings, and expects strings as inputs to
queries. So, keeping the ids as strings was easy initially, but it means that
you can't tell from the type whether it should be quoted, or not...
Therefore, handle ids as strings, converting them to numbers when they're
fetched from the database, and back to strings as part of the queries.
|
|
|
|
| |
By using insert-missing-data-and-return-all-ids.
|
|
|
|
| |
Through using insert-missing-data-and-return-all-ids.
|
|
|
|
| |
As this now supports inserting sets of data.
|
|
|
|
|
|
| |
Use exec-query-with-null-handling to distinguish NULL values, change it to
just take a list of fields and remove the handlers. Also, add a sets-of-data?
parameter so that this can be used licenses.
|
|
|
|
|
|
|
|
|
| |
PQgetvalue used by squee returns null values as empty strings, which are
ambiguous for string fields. Therefore, use PQgetisnull to implement a
serialiser for squee which checks empty strings to see if they're actually a
NULL value, then returns '() in this case.
exec-query-with-null-handling can be used to access this behaviour.
|
|
|
|
| |
As these values are not from the database, which is why they're not strings.
|
|
|
|
| |
These should be symbols, not just placeholders.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
To associate a set of lint checkers with a specific revision. While there is
the association through the lint warnings, that only works for checkers where
there are lint warnings for that revision.
Therefore, to allow finding all the checkers for a specific revision, also
associate them directly with the revision.
|
|
|
|
|
|
|
|
| |
The first field is now a <derivation> record, rather than a store path for the
derivation.
It's probably not necessary to cope with two versions, but this is what I've
done currently.
|
|
|
|
| |
As this is useful to know.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When loading data from an inferior Guix, first build it's latest version of
glibc-locales, and include that in the environment from the inferior.
This improves locale support, which is currently relevant for extracting lint
warnings.
Without this change, you'd only be able to switch to locales supported by the
glibc-utf8-locales package, assuming that the right version is available.
|
|
|
|
| |
In the load-new-guix-revision module.
|
|
|
|
| |
In the load-new-guix-revision module.
|
| |
|
|
|
|
|
| |
To return counts of lint warnings, grouped by lint checker for a specific
revision.
|
|
|
|
|
|
|
|
|
|
| |
This commit adds the relevant tables and code to store lint warnings in the
database.
Currently, only lint checkers which don't require access to the network will
be run, as this allows the processing to happen without network access. Also,
this functionality won't work in older versions of Guix which don't expose the
lint warnings in a compatible way.
|
|
|
|
|
| |
To increase the log output speed, avoiding inserting one character at a time
in to the database.
|
|
|
|
|
| |
This should help greatly with populating the database with new entries, and
greatly reduce code duplication.
|
| |
|
| |
|
|
|
|
| |
Rather than an id wrapped in a list.
|
| |
|
| |
|
|
|
|
| |
As there isn't sufficient data to make this work yet.
|