| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
To keep the page length down. All branches can still be seen on the page for
specific repositories.
|
|
|
|
| |
The git_branches.commits column doesn't allow NULL values.
|
|
|
|
|
|
|
|
|
|
|
| |
The git_branches table had 'NULL' values for some commits where the branch was
deleted, importantly this was the string 'NULL', not an actual NULL value.
This commit fixes that, migrating the existing values to be '', and changing
the relevant code.
The primary key is also extended to include the datetime field, as this is
important to allow a branch to be deleted twice.
|
|
|
|
| |
This happens when the repl can't be loaded for example.
|
|
|
|
|
| |
Older versions of the glibc-locales package just contain the UTF-8 variants,
not utf8.
|
| |
|
|
|
|
|
| |
This is a recent addition, so to support loading revisions without it, better
handle the error when loading the module.
|
|
|
|
| |
Otherwise modules from outside of the inferior can leak in.
|
|
|
|
|
| |
Using the title element, as the identifier is internal, but it's useful for
development to be able to find it out, if you want to run the job for testing.
|
| |
|
|
|
|
| |
To provide a more visual view of when the package versions were available.
|
|
|
|
|
| |
This is useful when looking back through history at what package versions were
previously available.
|
|
|
|
|
|
|
| |
This isn't new information, but derived from information already in the
database. It's collected here to make querying faster.
The table is updated when each new revision is entered.
|
|
|
|
|
|
|
|
| |
Previously, if you searched for packages like Ruby or Guile, the actual Ruby
and Guile packages would be low in the rankings, as the terms Ruby or Guile
don't appear much in the descriptions.
Therefore, change the ordering to make these exact matches appear higher up.
|
| |
|
| |
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|