Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Python: QSqlTableModel works on Windows but not on macOS

Python: QSqlTableModel works on Windows but not on macOS

Scheduled Pinned Locked Moved Unsolved General and Desktop
23 Posts 4 Posters 7.4k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D DrTiaZ

    Certainly, you are right.

    This is the MySQL server that I am pointing to:

    Schermata 2022-08-20 alle 19.09.21.png

    It is reacheable using Terminal from macOS. There are no other databases call "test". As you can see, it contains 3 tables. Specifically, "canzoni" has 3 fields (canzoni_id, titolo, album_id).

    I'm going to show you the best proof I can provide to ensure that I am operating on the correct server.

    As you can see, the table "canzoni" contains the following 7 rows:

    Schermata 2022-08-20 alle 19.11.09.png

    Now, if I try to execute an INSERT INTO statement via my script, using these lines

                query_to_execute = "INSERT INTO canzoni (titolo, album_id) VALUES ('Test1', '1')"
                query = QtSql.QSqlQuery(query_to_execute, db=db)
    

    the application correctly insert the new data into "canzoni".
    Schermata 2022-08-20 alle 19.13.51.png

    So I can suppose that ODBC driver works correctly, my application is able to point the correct server and also to query it.

    The problem using macOS is only to retrieve data from it.

    If I try

    SELECT COUNT(*) FROM canzoni;
    

    the result is

    Schermata 2022-08-20 alle 19.36.19.png

    JonBJ Online
    JonBJ Online
    JonB
    wrote on last edited by
    #14

    @DrTiaZ
    Any reason you chose not to try the SELECT 1, 2, 3 I suggested? That's why I typed it in....

    D 1 Reply Last reply
    0
    • JonBJ JonB

      @DrTiaZ
      Any reason you chose not to try the SELECT 1, 2, 3 I suggested? That's why I typed it in....

      D Offline
      D Offline
      DrTiaZ
      wrote on last edited by
      #15

      @JonB
      Sorry, I forgot to upload the last pic. This is the result

      Schermata 2022-08-20 alle 20.42.09.png

      JonBJ 1 Reply Last reply
      0
      • D DrTiaZ

        @JonB
        Sorry, I forgot to upload the last pic. This is the result

        Schermata 2022-08-20 alle 20.42.09.png

        JonBJ Online
        JonBJ Online
        JonB
        wrote on last edited by
        #16

        @DrTiaZ
        That implies to me that it is succeeding in retrieving the result set (rows) from the query from the database --- as opposed to never retrieving data. Don't know where that leaves you for your case though. Nor why Number of rows keeps being reported as -1.

        1 Reply Last reply
        0
        • D Offline
          D Offline
          DrTiaZ
          wrote on last edited by
          #17

          But also SELECT 1, 2, 3 fails to retrieve the queryset, in facts it retrieve only columns name and 0 row(s), like the queries before.

          Documentation relative to QtSql.QSqlQuery.size() says "Returns the size of the result (number of rows returned), or -1 if the size cannot be determined or if the database does not support reporting information about query sizes. Note that for non-SELECT statements ( isSelect() returns false ), will return -1. If the query is not active ( isActive() returns false ), -1 is returned."

          I really don't understand why this happens.

          Christian EhrlicherC JonBJ 2 Replies Last reply
          0
          • D DrTiaZ

            But also SELECT 1, 2, 3 fails to retrieve the queryset, in facts it retrieve only columns name and 0 row(s), like the queries before.

            Documentation relative to QtSql.QSqlQuery.size() says "Returns the size of the result (number of rows returned), or -1 if the size cannot be determined or if the database does not support reporting information about query sizes. Note that for non-SELECT statements ( isSelect() returns false ), will return -1. If the query is not active ( isActive() returns false ), -1 is returned."

            I really don't understand why this happens.

            Christian EhrlicherC Offline
            Christian EhrlicherC Offline
            Christian Ehrlicher
            Lifetime Qt Champion
            wrote on last edited by
            #18

            @DrTiaZ said in Python: QSqlTableModel works on Windows but not on macOS:

            I really don't understand why this happens.

            I would blame the ODBC driver then.

            Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
            Visit the Qt Academy at https://academy.qt.io/catalog

            1 Reply Last reply
            0
            • D DrTiaZ

              But also SELECT 1, 2, 3 fails to retrieve the queryset, in facts it retrieve only columns name and 0 row(s), like the queries before.

              Documentation relative to QtSql.QSqlQuery.size() says "Returns the size of the result (number of rows returned), or -1 if the size cannot be determined or if the database does not support reporting information about query sizes. Note that for non-SELECT statements ( isSelect() returns false ), will return -1. If the query is not active ( isActive() returns false ), -1 is returned."

              I really don't understand why this happens.

              JonBJ Online
              JonBJ Online
              JonB
              wrote on last edited by
              #19

              @DrTiaZ said in Python: QSqlTableModel works on Windows but not on macOS:

              But also SELECT 1, 2, 3 fails to retrieve the queryset, in facts it retrieve only columns name and 0 row(s), like the queries before.

              Ah, yes. I was expecting "No column name" as the titles for each column and thought the row shown was the single data row, but I think you're right.

              I don't know where you go next, or what help you will get here. Does MacOS supply an ODBC tool to allow you to query/view the data?

              1 Reply Last reply
              0
              • D Offline
                D Offline
                DrTiaZ
                wrote on last edited by
                #20

                @Christian-Ehrlicher said in Python: QSqlTableModel works on Windows but not on macOS:

                @DrTiaZ said in Python: QSqlTableModel works on Windows but not on macOS:

                I really don't understand why this happens.

                I would blame the ODBC driver then.

                I thought the same, but as @JonB suggested before, using iODBC tool and connecting to MySQL server via ODBC 8.0 Unicode Driver (same driver used in my Py script) I can view the data.

                Schermata 2022-08-20 alle 21.21.52.png

                JonBJ 1 Reply Last reply
                0
                • Christian EhrlicherC Offline
                  Christian EhrlicherC Offline
                  Christian Ehrlicher
                  Lifetime Qt Champion
                  wrote on last edited by
                  #21

                  I'm not aware of any such problems in the ODBC driver since ages so I doubt it's a Qt problem.

                  Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
                  Visit the Qt Academy at https://academy.qt.io/catalog

                  1 Reply Last reply
                  0
                  • D DrTiaZ

                    @Christian-Ehrlicher said in Python: QSqlTableModel works on Windows but not on macOS:

                    @DrTiaZ said in Python: QSqlTableModel works on Windows but not on macOS:

                    I really don't understand why this happens.

                    I would blame the ODBC driver then.

                    I thought the same, but as @JonB suggested before, using iODBC tool and connecting to MySQL server via ODBC 8.0 Unicode Driver (same driver used in my Py script) I can view the data.

                    Schermata 2022-08-20 alle 21.21.52.png

                    JonBJ Online
                    JonBJ Online
                    JonB
                    wrote on last edited by
                    #22

                    @DrTiaZ
                    I'm with @Christian-Ehrlicher on this, though we can't say 100%. If you are able, you might try PyQt5 or 6, or even C++ if you can, to rule out PySide. Otherwise reinstall Qt and/or the ODBC driver/Python interface to that. Or even try a different version of Qt. And search to verify no known MacOS Qt/Py/ODBC issues. Or even a different MacOS machine if available! Other than that I'm not sure how much more help you can get here.

                    1 Reply Last reply
                    0
                    • D Offline
                      D Offline
                      DrTiaZ
                      wrote on last edited by
                      #23

                      Thank you, I'll make some test, even on a different macOS machine. Unfortunately, I am not so skilled with C++.
                      I'll let you know!

                      1 Reply Last reply
                      0

                      • Login

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Users
                      • Groups
                      • Search
                      • Get Qt Extensions
                      • Unsolved