Repository navigation
TSqlMapManager version property and cache validity check - #10
Merged
Merged
Conversation
… built by another version
This was referenced Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TSqlMapManager::VERSIONholds the package version (1.0.0).TSqlMapManager::getVersion()(theVersionproperty) returns the version that built the manager, in the form ofPrado::getVersion(). It is serialized with the manager, so a manager restored from the application cache reports the version that wrote the entry, ornullfor an entry written by the framework copy.TSqlMapConfigdiscards a cached manager whose version is notVERSIONand rebuilds it from the config files. The migration guide no longer asks for a cache clear after upgrading.TSqlMapConfigreusing a current cached manager and replacing a stale one.