@JonB After add the QT_DEBUG_PLUGINS=1 The cmd show this and i see that QMYSQL is same with another sql. So I don't know @@ qt.core.plugin.factoryloader: Got keys from plugin meta data QList("QSQLITE") qt.core.plugin.factoryloader: looking at "qsqlmimer.dll" qt.core.plugin.loader: Found metadata in lib C:/Qt/6.8.3/mingw_64/plugins/sqldrivers/qsqlmimer.dll, metadata= { "IID": "org.qt-project.Qt.QSqlDriverFactoryInterface", "MetaData": { "Keys": [ "QMIMER" ] }, "archlevel": 2, "className": "QMimerSQLDriverPlugin", "debug": false, "version": 395264 } qt.core.plugin.factoryloader: Got keys from plugin meta data QList("QMIMER") qt.core.plugin.factoryloader: looking at "qsqlmysql.dll" qt.core.plugin.loader: Found metadata in lib C:/Qt/6.8.3/mingw_64/plugins/sqldrivers/qsqlmysql.dll, metadata= { "IID": "org.qt-project.Qt.QSqlDriverFactoryInterface", "MetaData": { "Keys": [ "QMYSQL", "QMARIADB" ] }, "archlevel": 2, "className": "QMYSQLDriverPlugin", "debug": false, "version": 395264 } qt.core.plugin.factoryloader: Got keys from plugin meta data QList("QMYSQL", "QMARIADB") qt.core.plugin.factoryloader: looking at "qsqlodbc.dll" qt.core.plugin.loader: Found metadata in lib C:/Qt/6.8.3/mingw_64/plugins/sqldrivers/qsqlodbc.dll, metadata= { "IID": "org.qt-project.Qt.QSqlDriverFactoryInterface", "MetaData": { "Keys": [ "QODBC" ] }, "archlevel": 2, "className": "QODBCDriverPlugin", "debug": false, "version": 395264 } qt.core.plugin.factoryloader: Got keys from plugin meta data QList("QODBC") qt.core.plugin.factoryloader: looking at "qsqlpsql.dll"

Hi, You can also check out this library: 👉 QAudioTagReader It’s a Qt-friendly wrapper around TagLib for exporting audio tags.

In QT Design Studio, Tab Buttons are mostly for navigation within the UI, but each tab doesn’t automatically hide other content. Usually, a StackView or Loader is needed to switch visible content depending on the active tab.

@IamSumit can you reproduce the issue and share the Support Information logs. Please refer to the following Knowledge Base Article regarding how to obtain the Support Information is https://qatools.knowledgebase.qt.io/misc/collecting-support-info/collecting-support-information-linux-mac-windows/

Hello! I have recently systematically studied the content related to QML modular development using CMake under Qt 6.8, and tried to write a set of configurations. To ensure that the project structure is clear, complies with modern CMake specifications, and avoids potential hidden dangers in subsequent maintenance, I hope to invite experienced friends to help review my configuration ideas and implementation details to see if there are any non-standard, optimizable, or missing parts. Project structure: D:\PROJECT\QT\MODERNTEST | CMakeLists.txt | \---src CMakeLists.txt Images.qrc main.cpp Test.qml Global CMakeLists.txt： cmake_minimum_required(VERSION 3.16) project(ModernTest VERSION 0.1 LANGUAGES CXX) set(CMAKE_CXX_STANDARD 17) set(CMAKE_CXX_STANDARD_REQUIRED ON) set(CMAKE_AUTORCC ON) find_package(Qt6 6.8 REQUIRED COMPONENTS Quick) qt_standard_project_setup(REQUIRES 6.8) add_subdirectory(src) Sub CMakeLists.txt： add_executable(${PROJECT_NAME} main.cpp ) qt_add_qml_module(${PROJECT_NAME} URI QMLApp VERSION 0.1 QML_FILES Test.qml RESOURCES Images.qrc ) set_target_properties(${PROJECT_NAME} PROPERTIES MACOSX_BUNDLE TRUE WIN32_EXECUTABLE TRUE ) target_link_libraries(${PROJECT_NAME} PRIVATE Qt6::Quick ) install(TARGETS ${PROJECT_NAME} BUNDLE DESTINATION . LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR} RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR} ) main.cpp #include <QGuiApplication> #include <QQmlApplicationEngine> int main(int argc, char* argv[]){ QGuiApplication a(argc,argv); QQmlApplicationEngine engine; engine.loadFromModule("QMLTest","Test"); return a.exec(); } The above is the configuration I organized based on what I learned in class and the official manual. To ensure compliance with modern CMake specifications and avoid potential issues, I sincerely ask all experts to kindly offer their advice and check if there are any omissions or "modern" techniques that can be optimized.

I do a lot of python/pyqt database access using psycopg2 for PostgreSQL. It's so much easier to prototype these kinds of ideas in a language like python, and if needed then port it to c++, but truth be told, most of the time the python app is just works as is so no need to rewrite in c++. For something as simple as you are alluding to, the hard core OO models using DAO/DTO are probably overkill. Also, when dealing qith SQL queries it's "nice" to work in a language that is NOT strongly typed. Sorry if this is a round-about way to respond. Your path has merit in the realm of intellectual curiosity, but if you want it done quickly then python is a better option, and you can still wrap it in a Qt GUI. Yikes! Didn't notice OP was 9 months ago...

https://www.qt.io/contact-us/qt-offices Local Office - Shanghai China Room 3306-3307, 33F No.3 Hongqiao Road, Grand Gateway Tower 2 Xuhui District, Shanghai P.R.China, 200030 Sales inquiries +86 21 51748525 Administration inquiries tel. +86 21 51748525 fax +86 21 51748526 china@qt.io

Hi, I think you can use https://forum.qt.io/category/5/qt-io-webservices category for this type of question (moved there by the way). Are these in your "unread" section ? Are they marked as you following them ?