deprecate: Raise deprecation levels of API elements #2208
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Summary of the change: Raise the deprecation levels of API from more than 3 releases ago.
Detailed description:
The following elements had most recent level change in release 0.46.0 (January 2024) ->
Raise from WARNING to ERROR:
FieldSet.select(where)
FieldSet.selectBatched()
FieldSet.selectAllBatched()
Query.adjustSlice()
ColumnSet.slice()
The following elements had most recent level change in release 0.50.0 (April 2024) ->
Raise from WARNING to ERROR:
Database.connectPool()
DatabaseConfig.defaultRepetitionAttempts
andTransaction.repetitionAttempts
DatabaseConfig.defaultMinRepetitionDelay
andTransaction.minRepetitionDelay
DatabaseConfig.defaultMaxRepetitionDelay
andTransaction.maxRepetitionDelay
Currently HIDDEN, now removed:
ExposedDatabaseMetadata
interface propertycurrentScheme
Additional:
The original
buildSrc/Versions
object was also raised to ERROR in release 0.50.0 (April 2024). It has now been removed.Type of Change
Please mark the relevant options with an "X":
Affected databases:
Checklist
Related Issues