Feature testing through Database::supports(Feature) #81

New issue

Closed

opened 2026-09-30 19:10:54 +02:00 by c.fahner · 0 comments

c.fahner commented

2026-09-30 19:10:54 +02:00

Owner

Currently the only feature that can be tested is schema enforcement using the SchemaEnforceable interface. However, there are many more schema-related features which databases can optionally support. Moreover, not all optional features are schema-related and in the future it might also become necessary to test for subfeatures. Which features are required or recommended also differs per application. A more general mechanism for feature testing needs to be made available.

The Database interface should instead have a runtime method supports(Database\Feature):bool, where Feature is an enum to which features can be added progressively.

Implementors may do a feature check during their regular database install/upgrade process.

This means SchemaEnforceable can be removed, to be replaced by Database::applySchema($collectionName, $schema):UpgradeCommand which just applies as many schema rules as it can.

Currently the only feature that can be tested is schema enforcement using the `SchemaEnforceable` interface. However, there are many more schema-related features which databases can optionally support. Moreover, not all optional features are schema-related and in the future it might also become necessary to test for subfeatures. Which features are required or recommended also differs per application. A more general mechanism for feature testing needs to be made available. The `Database` interface should instead have a runtime method `supports(Database\Feature):bool`, where `Feature` is an `enum` to which features can be added progressively. Implementors may do a feature check during their regular database install/upgrade process. This means `SchemaEnforceable` can be removed, to be replaced by `Database::applySchema($collectionName, $schema):UpgradeCommand` which just applies as many schema rules as it can.

c.fahner added this to the v0.2 milestone

2026-09-30 19:10:54 +02:00

c.fahner added the

Kind/Enhancement

label

2026-09-30 19:10:54 +02:00

c.fahner started working

2026-10-19 17:26:01 +02:00

c.fahner referenced this issue from a pull request that will close it,

2026-10-19 18:04:33 +02:00

Database feature testing #88

c.fahner stopped working