CollectionStore

Check if a user can query a collection.

This considers the effective permissions (with inheritance).

Count chunks in a collection.

Count documents in a collection.

Create a new collection.

Validates that:

• The parent exists (if not a root collection)
• Permissions don't loosen parent restrictions
• The path is valid and not already taken

Delete a collection.

The collection must be empty (no documents or sub-collections).

Ensure a collection exists, creating it if necessary.

Creates parent collections as needed (as public, non-leaf).

Find collections accessible by user matching a pattern.

This is the key permission-filtered query used during search. Returns only collections where:

• Pattern matches, AND
• User has access (public OR user's principals overlap with queryableBy)

Also respects inheritance - if a parent is not accessible, its children are also not accessible.

Get a collection by path.

Get a collection by its database ID.

Get effective permissions for a collection considering inheritance.

Effective permissions are the intersection of:

• The collection's own queryableBy, AND
• All ancestor collections' queryableBy sets

If any ancestor is public (empty queryableBy), that level is skipped. If the collection itself is public, returns empty (meaning public).

List all collections matching a pattern.

Does NOT apply permission filtering - returns all matching collections. Use findAccessible for permission-filtered queries.

List direct children of a collection.

Get collection statistics.

Update collection metadata.

Update collection permissions.

Validates that new permissions don't loosen parent restrictions.

Check if a collection exists.