1.6.0-ls220

LinuxServer Changes:

Rebase to Alpine 3.19.

PIP Changes:

Updating PIP version of beets to 1.6.0

nightly-c75f07a0-ls32

LinuxServer Changes:

Rebase to Alpine 3.19.

beets Changes:

Define paths to lint in mypy configuration

1.6.0-ls219

LinuxServer Changes:

Rebase to Alpine 3.19.

PIP Changes:

Updating PIP version of beets to 1.6.0

nightly-c75f07a0-ls31

LinuxServer Changes:

Rebase to Alpine 3.19.

beets Changes:

Define paths to lint in mypy configuration

1.6.0-ls218

LinuxServer Changes:

Rebase to Alpine 3.19.

PIP Changes:

Updating PIP version of beets to 1.6.0

nightly-c75f07a0-ls30

LinuxServer Changes:

Rebase to Alpine 3.19.

beets Changes:

Define paths to lint in mypy configuration

nightly-c75f07a0-ls29

LinuxServer Changes:

Rebase to Alpine 3.19.

beets Changes:

Define paths to lint in mypy configuration

nightly-4354ba4f-ls28

LinuxServer Changes:

Rebase to Alpine 3.19.

beets Changes:

Merge pull request #5214 from beetbox/handle-null-path

Handle NULL values in the path column

nightly-34a59f98-ls28

LinuxServer Changes:

Rebase to Alpine 3.19.

beets Changes:

Merge pull request #5210 from snejus/add-in-query-and-remove-named-query

Enforce the same interface across all ...Query implementations

Make PlaylistQuery a FieldQuery

While working on the DB optimization and looking at updates upstream I discovered one query which does not follow the FieldQuery interface —PlaylistQuery, so I looked into it in more detail and ended up integrating it as a FieldQuery.

One special thing about it is that it uses IN SQL operator, so I added implementation for this sort of query outside the playlist context, see InQuery.

Otherwise, it seems like PlaylistQuery is a field query with a special way of resolving values it wants to query. In the future, we may want to consider moving this kind of custom initialization logic away from init methods to factory/@classmethod: this should make it more clear that the purpose of such logic is to resolve the data that is required to define a particular FieldQuery class fully.

Remove NamedQuery since it is unused

This simplifies query parsing logic in queryparse.py. We know that this logic can only receive FieldQuery classes thus I adjusted types and removed the logic that handles other cases.

Effectively, this means that the query parsing logic does not need to care whether the query is named by the corresponding DB field. Instead, queries like SingletonQuery and PlaylistQuery are initialized with the same data as others and take things from there themselves: in this case they translate singleton and playlist queries to the underlying DB filters.

nightly-329098a0-ls28

LinuxServer Changes:

Rebase to Alpine 3.19.

beets Changes:

Merge pull request #5220 from snejus/improve-build-output-and-coverage

Improve GitHub build output and configure coverage