Object relational mapping in HMI development with Qt
summary
An LGPLv3 Qt module named Qt ORM implements an object–relational layer using the Qt Meta-Object System and Qt SQL/SQLite, requires C++17, and is currently a prototype that is SQLite-only and single-threaded. It auto-generates schema, exposes a session with merge/transaction/rollback, returns QVector<T> domain objects with eager fetching, and lets you build filters as C++ expressions instead of SQL strings. It aims for embedded use (not for very large tables ~100k+ rows) and crashes on mapping inconsistencies to fail fast.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:39Agenda
- 2:37Structured data
- 3:35Data model
- 5:07Database modeling
- 6:18SQL
- 6:41Reading code
- 8:08Telemetry
- 9:13Data models
- 11:18Object relational libraries
- 13:53Disadvantages
- 15:08Why Qt
- 17:39QtRM
- 18:52Qt default constructor
- 19:34Example project
- 20:00Creating domain classes
- 20:55Creating ORM sessions
- 21:51Creating two engines
- 22:44Updating the database
- 23:15Transactions
- 24:04Rollback
- 24:23Cure
- 25:28Filter
- 26:06Run
- 26:23Remove
- 26:39Summary
related talks
28mImplementing Modern Design Patterns with Qt
28mModel-based HMI development using Qt
49mHow to scale QML based projects an Architecture vision
01h 21mAdvanced Qt - A Deep Dive 6/6 - ModelView Part 2
01h 16mQt Apps with Nokia - Design, Develop, Distribute 5/7, Getting the most of Device
01h 30m“Qt as a C++ Framework: History, Present State and Future”
27mCoding Qt for greater interoperability and portability ...
02h 16mWORKSHOP: Back to Basics: writing a model