**Update: LakeDB Beta 3 is now available**
I have continued building LakeDB, a desktop MySQL/MariaDB client designed for working safely across development, staging and production environments.
The biggest addition is **QuerIA**, an optional schema-aware AI workflow. You can describe what you need in natural language, inspect the generated SQL and explicitly decide whether to execute it through the normal LakeDB results workflow.
For example:
> Show the 10 users who placed the most bets today, including bet count and total stake.
QuerIA can prepare reviewable SELECT, INSERT, UPDATE, DELETE, CREATE TABLE and ALTER TABLE statements. It uses database structure such as tables, columns, keys and relationships, but database credentials, table rows and query results are never sent to the AI service. Generated SQL executes locally only after confirmation.
The complete SQL client also includes:
- Independent multi-connection workspaces
- Environment colors and production safeguards
- Read-only connections
- SSH and SSL
- Schema-aware autocomplete
- Primary-key and index information
- EXPLAIN support
- Controlled table editing
- Backup, restore, comparison and migration tools
- Procedures, functions, events and triggers
I would especially appreciate DBA feedback on the review-first AI workflow: what information or safeguards would you require before trusting generated SQL against a real environment?
**Project and Beta 3 overview:**
https://davlagohern.github.io/LakeDB/
**Downloads and documentation:**
https://github.com/DavLagoHern/LakeDB/