Use Cases + security and stability update @ Server @ MentDB Weak

This release includes important security fixes, stability improvements and bug fixes.
All users are strongly encouraged to update.

What's new
  • Use Cases: a new page with 913 real examples for 91 profiles (programming, sciences, chemistry, space and energy, engineering, AI, documents and integration, operations, business). Each example chains MQL functions and shows the result it returned on a MentDB server.
  • Every function name in the code examples of the MQL Functions reference and of the Use Cases now opens its documentation.
  • New option bot set_min_score: minimum score for a bot to answer, below it the bot gives its "not found" response.
  • New optional language for date dayname and date monthname (en, fr, es, de, pt-BR...).
  • Physical constants updated to CODATA 2022.
  • Many fixes in the MQL functions (jobs, scripts, SCRUD, files, Excel, strings, dates, statistics, versioning) and in the documentation.
Upgrade notes
  • From 4.2.2: copy the new src, core and docs folders, then restart. From an older version, follow the notes of 4.2.2 (all the folders and the bundled Java 21).
  • Before any upgrade, back up the cert and conf folders, and never delete the data folder.
  • The database schema is upgraded automatically at startup.
  • Behavior changes:
    • string md5 and string sha return the standard hash: a value stored with an older version may differ (leading zeros, accented characters).
    • job add with an active job schedules it at once (no job resume needed), job update applies at once and job remove stops the job.
    • The SCRUD services generated for H2 and PostgreSQL now use the primary key of the table.
    • Excel numbers keep all their decimals (at least 2 as before).
    • constant physics_* return the CODATA 2022 values; exact constants are shown without uncertainty.
    • metric date returns a JSON array, and file mkdir creates the missing parent folders.
    • Bots answer only above a minimum score (200 by default, see bot set_min_score).
start: 2026-11-01end: 2026-11-01v_start: 423v_end: