select code from modules
where function eq 'sort'
and type eq 'in-place'
and version >= 3.7;
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco.
Rule 1 has a caveat! -- Who broke the cabal?
| [reply]
[d/l] |
That's not versioning, it's a query.
I thought database versioning was one of the "classic hard problems" with databases. Have you found a magical solution to this problem that the rest of us have missed? I look forward to your "modicum of imagination" on this topic.
| [reply] |
I thought database versioning...
Re-read the context. Modules have version numbers. Sometimes you need to retain access to an older version of a module for one application, whilst moving to using the latest version for new applications. Retaining access to both (or more) versions of the module within the same Perl installation is a problem not currently easily addressable.
The simple expedient of adding a "Version" field to the "Modules" table would allow each application to request any of: the latest version; a specified version; any version before (or after) a given version; etc.
In this context, I chose the word "versioning" to describe that possibility.
Whatever other interpretation you have chosen to read into my use of that word in this context--is wrong.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco.
Rule 1 has a caveat! -- Who broke the cabal?
| [reply] |