Query Timeout if "too many" columns are selected #1485
              
                Unanswered
              
          
                  
                    
                      johnweidauer
                    
                  
                
                  asked this question in
                Q&A
              
            Replies: 1 comment
-
| 
 There's nothing in MySqlConnector that enforces a limit; it sends the query to the server, then waits for the response to come in over the network. A timeout generally indicates that no such response was received in time. It's hard to speculate about what might be happening but could there be some component between the database server and your application that drops packets over a certain size? | 
Beta Was this translation helpful? Give feedback.
                  
                    0 replies
                  
                
            
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
-
I have a query that returns data, but if I include too many columns in my web application using mysqlconnector, it will timeout. I have written this query both is plain text and in a procedure, but when more than 15 columns are to be returned, timeout. Is there a column limit, or a size limit on the return? I have tried searching for this topic, but was unable to find anything. Can anyone tell me if this is a column limit or a size limit. The query in question is only returning 1 row of all columns. *This table was not created by me and is a table created by the vendor, but I do have access to make modifications to both the table and MySQL Server 5.7.
My Schema:
CarrierKeyint(11) NOT NULL AUTO_INCREMENT,codevarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,name_companyvarchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,addressvarchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,cityvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,state_codevarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,zipvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,phonevarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,faxvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,contactvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,fee_schedulevarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,classvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,feesvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT 'STAND',edi_formatvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,code_paymentvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,code_payment2varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,code_adjustmentvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,receiver_typevarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,code_categoryvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,claim_filingvarchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,payer_id_profvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,unique_provider_idvarchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,network_statusvarchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT NULL,state_specificvarchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NULL DEFAULT ''Beta Was this translation helpful? Give feedback.
All reactions