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. QSqlQuery error with translated text
Forum Updated to NodeBB v4.3 + New Features

QSqlQuery error with translated text

Scheduled Pinned Locked Moved Solved General and Desktop
24 Posts 4 Posters 2.6k Views 2 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.
  • SGaistS Offline
    SGaistS Offline
    SGaist
    Lifetime Qt Champion
    wrote on last edited by
    #2

    Hi,

    Using prepared query has nothing to do with UTF8 management. It's a way to avoid SQL injection by stringing together your query from various input.

    One thing you should check is whether your database setup supports the charset you want to use.

    On a side note, you might want to take into account that translating that kind of messages may also force you to write tools that are able to extract useful data from them in several languages as well. Showing translated messages to a user is one thing, doing that as part of your system logging might be counter-productive.

    Interested in AI ? www.idiap.ch
    Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

    SPlattenS 1 Reply Last reply
    5
    • SGaistS SGaist

      Hi,

      Using prepared query has nothing to do with UTF8 management. It's a way to avoid SQL injection by stringing together your query from various input.

      One thing you should check is whether your database setup supports the charset you want to use.

      On a side note, you might want to take into account that translating that kind of messages may also force you to write tools that are able to extract useful data from them in several languages as well. Showing translated messages to a user is one thing, doing that as part of your system logging might be counter-productive.

      SPlattenS Offline
      SPlattenS Offline
      SPlatten
      wrote on last edited by
      #3

      @SGaist , on start-up the splash screen displays what its doing, this is the text that is being translated, it goes ok until it gets to:

      Training Server connected to database
      

      The French translation I have for this message is:

      Serveur de formation connecté à la base de données
      

      How do I know what charset is required for this language?

      Kind Regards,
      Sy

      KroMignonK JonBJ 2 Replies Last reply
      0
      • SPlattenS SPlatten

        @SGaist , on start-up the splash screen displays what its doing, this is the text that is being translated, it goes ok until it gets to:

        Training Server connected to database
        

        The French translation I have for this message is:

        Serveur de formation connecté à la base de données
        

        How do I know what charset is required for this language?

        KroMignonK Offline
        KroMignonK Offline
        KroMignon
        wrote on last edited by
        #4

        @SPlatten said in QSqlQuery error with translated text:

        How do I know what charset is required for this language?

        AFAIK, Qt internally always use UTF-8. If it is in Qt application, there is nothing to do.
        The question is how to do get the message to display?

        It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

        SPlattenS 1 Reply Last reply
        1
        • KroMignonK KroMignon

          @SPlatten said in QSqlQuery error with translated text:

          How do I know what charset is required for this language?

          AFAIK, Qt internally always use UTF-8. If it is in Qt application, there is nothing to do.
          The question is how to do get the message to display?

          SPlattenS Offline
          SPlattenS Offline
          SPlatten
          wrote on last edited by
          #5

          @KroMignon , the actual error is occurring not in the display of the error, which is displayed, but in trying to add the parameter to the stored procedure.

          Kind Regards,
          Sy

          1 Reply Last reply
          0
          • SPlattenS SPlatten

            @SGaist , on start-up the splash screen displays what its doing, this is the text that is being translated, it goes ok until it gets to:

            Training Server connected to database
            

            The French translation I have for this message is:

            Serveur de formation connecté à la base de données
            

            How do I know what charset is required for this language?

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

            @SPlatten
            I would start by Googling, say, MariaDB French text. I do not know the ins & outs, but Accented characters in mySQL table seems related to your behaviour. What about In MySQL, never use “utf8”. Use “utf8mb4”?

            SPlattenS 1 Reply Last reply
            3
            • JonBJ JonB

              @SPlatten
              I would start by Googling, say, MariaDB French text. I do not know the ins & outs, but Accented characters in mySQL table seems related to your behaviour. What about In MySQL, never use “utf8”. Use “utf8mb4”?

              SPlattenS Offline
              SPlattenS Offline
              SPlatten
              wrote on last edited by
              #7

              @JonB , is there a similar issue with TEXT parameters? I've modified the database/table creating procedure replacing:

              COLLATE=''uft8_general_ci'
              

              with:

              COLLATE='utf8mb4_unicode_ci'
              

              I've then dropped the database and recreated. Still getting the exact same error. Now though, where as before the error message was being logged, now that doesn't work either.

              Kind Regards,
              Sy

              KroMignonK 1 Reply Last reply
              0
              • SPlattenS SPlatten

                @JonB , is there a similar issue with TEXT parameters? I've modified the database/table creating procedure replacing:

                COLLATE=''uft8_general_ci'
                

                with:

                COLLATE='utf8mb4_unicode_ci'
                

                I've then dropped the database and recreated. Still getting the exact same error. Now though, where as before the error message was being logged, now that doesn't work either.

                KroMignonK Offline
                KroMignonK Offline
                KroMignon
                wrote on last edited by
                #8

                @SPlatten said in QSqlQuery error with translated text:

                I've then dropped the database and recreated. Still getting the exact same error. Now though, where as before the error message was being logged, now that doesn't work either.

                I think you also have to set the default charset for the SQL statements to UTF8.
                You can do I with SET NAMES 'utf8'; for each connection or via server configuration:

                [client]
                default-character-set=utf8
                
                [mysql]
                default-character-set=utf8
                
                [mysqld]
                collation-server = utf8_unicode_ci
                init-connect='SET NAMES utf8'
                character-set-server = utf8
                

                It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                SPlattenS 1 Reply Last reply
                0
                • KroMignonK KroMignon

                  @SPlatten said in QSqlQuery error with translated text:

                  I've then dropped the database and recreated. Still getting the exact same error. Now though, where as before the error message was being logged, now that doesn't work either.

                  I think you also have to set the default charset for the SQL statements to UTF8.
                  You can do I with SET NAMES 'utf8'; for each connection or via server configuration:

                  [client]
                  default-character-set=utf8
                  
                  [mysql]
                  default-character-set=utf8
                  
                  [mysqld]
                  collation-server = utf8_unicode_ci
                  init-connect='SET NAMES utf8'
                  character-set-server = utf8
                  
                  SPlattenS Offline
                  SPlattenS Offline
                  SPlatten
                  wrote on last edited by
                  #9

                  @KroMignon , these are the settings I need:

                  [client]
                   default-character-set = utf8mb4
                  
                   [mysqld]
                   character-set-server  = utf8mb4
                   collation-server      = utf8mb4_unicode_ci
                   character_set_server  = utf8mb4
                   collation_server      = utf8mb4_unicode_ci
                  

                  Just waiting for IT to unlock the laptop so I can implement.

                  Kind Regards,
                  Sy

                  KroMignonK 1 Reply Last reply
                  0
                  • SPlattenS SPlatten

                    @KroMignon , these are the settings I need:

                    [client]
                     default-character-set = utf8mb4
                    
                     [mysqld]
                     character-set-server  = utf8mb4
                     collation-server      = utf8mb4_unicode_ci
                     character_set_server  = utf8mb4
                     collation_server      = utf8mb4_unicode_ci
                    

                    Just waiting for IT to unlock the laptop so I can implement.

                    KroMignonK Offline
                    KroMignonK Offline
                    KroMignon
                    wrote on last edited by
                    #10

                    @SPlatten said in QSqlQuery error with translated text:

                    Just waiting for IT to unlock the laptop so I can implement.

                    Have you tried to use SET NAMES 'utf8'; ?

                    It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                    SPlattenS 1 Reply Last reply
                    0
                    • KroMignonK KroMignon

                      @SPlatten said in QSqlQuery error with translated text:

                      Just waiting for IT to unlock the laptop so I can implement.

                      Have you tried to use SET NAMES 'utf8'; ?

                      SPlattenS Offline
                      SPlattenS Offline
                      SPlatten
                      wrote on last edited by
                      #11

                      @KroMignon , what does that do?

                      Kind Regards,
                      Sy

                      KroMignonK 1 Reply Last reply
                      0
                      • SPlattenS SPlatten

                        @KroMignon , what does that do?

                        KroMignonK Offline
                        KroMignonK Offline
                        KroMignon
                        wrote on last edited by
                        #12

                        @SPlatten said in QSqlQuery error with translated text:

                        what does that do?

                        The same without having to change the server settings ;) ==> https://dev.mysql.com/doc/refman/8.0/en/set-names.html

                        It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                        SPlattenS 1 Reply Last reply
                        0
                        • KroMignonK KroMignon

                          @SPlatten said in QSqlQuery error with translated text:

                          what does that do?

                          The same without having to change the server settings ;) ==> https://dev.mysql.com/doc/refman/8.0/en/set-names.html

                          SPlattenS Offline
                          SPlattenS Offline
                          SPlatten
                          wrote on last edited by
                          #13

                          @KroMignon , why utf8 and not utf8mb4 ?

                          Kind Regards,
                          Sy

                          KroMignonK 1 Reply Last reply
                          0
                          • SPlattenS SPlatten

                            @KroMignon , why utf8 and not utf8mb4 ?

                            KroMignonK Offline
                            KroMignonK Offline
                            KroMignon
                            wrote on last edited by KroMignon
                            #14

                            @SPlatten said in QSqlQuery error with translated text:

                            why utf8 and not utf8mb4 ?

                            Sorry, you are right utf8mb4 is better. utf8 seems to be only a subset of UTF-8 charset! (cf https://mathiasbynens.be/notes/mysql-utf8mb4)

                            It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                            SPlattenS 1 Reply Last reply
                            1
                            • KroMignonK KroMignon

                              @SPlatten said in QSqlQuery error with translated text:

                              why utf8 and not utf8mb4 ?

                              Sorry, you are right utf8mb4 is better. utf8 seems to be only a subset of UTF-8 charset! (cf https://mathiasbynens.be/notes/mysql-utf8mb4)

                              SPlattenS Offline
                              SPlattenS Offline
                              SPlatten
                              wrote on last edited by
                              #15

                              @KroMignon , where would I use SET NAMES 'utf8umb4';

                              In the ini file or console ? I need a solution that works when the system starts or restart.

                              Kind Regards,
                              Sy

                              KroMignonK 1 Reply Last reply
                              0
                              • SPlattenS SPlatten

                                @KroMignon , where would I use SET NAMES 'utf8umb4';

                                In the ini file or console ? I need a solution that works when the system starts or restart.

                                KroMignonK Offline
                                KroMignonK Offline
                                KroMignon
                                wrote on last edited by
                                #16

                                @SPlatten said in QSqlQuery error with translated text:

                                where would I use SET NAMES 'utf8umb4';
                                In the ini file or console ? I need a solution that works when the system starts or restart.

                                You should send it to server after each new connection:

                                QSqlDatabase db = QSqlDatabase::addDatabase("QMYSQL");
                                db.setHostName("myhostname");
                                db.setDatabaseName("databasename");
                                db.setUserName("username");
                                db.setPassword("pasword");
                                bool ok = db.open()
                                if(ok)
                                {
                                    QSqlQuery query(db);
                                    query.exec("SET NAMES 'utf8umb4';");
                                }
                                

                                It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                                SPlattenS 1 Reply Last reply
                                2
                                • SPlattenS Offline
                                  SPlattenS Offline
                                  SPlatten
                                  wrote on last edited by
                                  #17

                                  Thank you, will give it a go now.

                                  Kind Regards,
                                  Sy

                                  1 Reply Last reply
                                  0
                                  • KroMignonK KroMignon

                                    @SPlatten said in QSqlQuery error with translated text:

                                    where would I use SET NAMES 'utf8umb4';
                                    In the ini file or console ? I need a solution that works when the system starts or restart.

                                    You should send it to server after each new connection:

                                    QSqlDatabase db = QSqlDatabase::addDatabase("QMYSQL");
                                    db.setHostName("myhostname");
                                    db.setDatabaseName("databasename");
                                    db.setUserName("username");
                                    db.setPassword("pasword");
                                    bool ok = db.open()
                                    if(ok)
                                    {
                                        QSqlQuery query(db);
                                        query.exec("SET NAMES 'utf8umb4';");
                                    }
                                    
                                    SPlattenS Offline
                                    SPlattenS Offline
                                    SPlatten
                                    wrote on last edited by
                                    #18

                                    @KroMignon , having implemented that, I'm still getting the same issue.

                                    Kind Regards,
                                    Sy

                                    KroMignonK 1 Reply Last reply
                                    0
                                    • SPlattenS SPlatten

                                      @KroMignon , having implemented that, I'm still getting the same issue.

                                      KroMignonK Offline
                                      KroMignonK Offline
                                      KroMignon
                                      wrote on last edited by KroMignon
                                      #19

                                      @SPlatten said in QSqlQuery error with translated text:

                                      having implemented that, I'm still getting the same issue.

                                      Out of curiosity, the SQL command you want to execute is CALL addAuditEntry("Serveur de formation connecté à la base de données");, right?

                                      Did you try to do it by hand, on command line or with phpMyAdmin/MySQL Workbench?

                                      It is an old maxim of mine that when you have excluded the impossible, whatever remains, however improbable, must be the truth. (Sherlock Holmes)

                                      SPlattenS 2 Replies Last reply
                                      0
                                      • KroMignonK KroMignon

                                        @SPlatten said in QSqlQuery error with translated text:

                                        having implemented that, I'm still getting the same issue.

                                        Out of curiosity, the SQL command you want to execute is CALL addAuditEntry("Serveur de formation connecté à la base de données");, right?

                                        Did you try to do it by hand, on command line or with phpMyAdmin/MySQL Workbench?

                                        SPlattenS Offline
                                        SPlattenS Offline
                                        SPlatten
                                        wrote on last edited by
                                        #20

                                        @KroMignon , I'm using HeidiSQL, will try now.

                                        Kind Regards,
                                        Sy

                                        1 Reply Last reply
                                        0
                                        • KroMignonK KroMignon

                                          @SPlatten said in QSqlQuery error with translated text:

                                          having implemented that, I'm still getting the same issue.

                                          Out of curiosity, the SQL command you want to execute is CALL addAuditEntry("Serveur de formation connecté à la base de données");, right?

                                          Did you try to do it by hand, on command line or with phpMyAdmin/MySQL Workbench?

                                          SPlattenS Offline
                                          SPlattenS Offline
                                          SPlatten
                                          wrote on last edited by
                                          #21

                                          @KroMignon , Now I'm confused, having put into HeidiSQL:

                                          CALL addAuditEntry("Serveur de formation connecté à la base de données");
                                          

                                          It works with no error reported, so why doesn't the same work when I do:

                                          QSqlQuery query;
                                          query.prepare("CALL addAuditEntry(?);");
                                          query.addBindValue(crstrEntry);
                                          query.exec();
                                          

                                          Kind Regards,
                                          Sy

                                          KroMignonK 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