From dev at academia.org.mx Mon Jan 16 15:21:13 2023 From: dev at academia.org.mx (Ramiro Santa Ana Anguiano) Date: Mon, 16 Jan 2023 12:21:13 -0800 Subject: [Tshwanelex-l] Fwd: Database connection not working In-Reply-To: <01507ade-6165-2388-6790-84095f031922@academia.org.mx> References: <01507ade-6165-2388-6790-84095f031922@academia.org.mx> Message-ID: <46b5d458-4574-6d7e-bb1d-ccc4298bfd19@academia.org.mx> Hi, I am writing on behalf of the Mexican Academy of Language and because we are having issues between TLex and our MySQL server. We are using TLex on Windows 7, version 14.1.0.3250 on evaluation mode. Our MySQL server is v 8. The ODBC connection is successful: The ODBC driver is for 64 bit, so we used? TLex 64 bit version. Unfortunately, when we try to save any dictionary, with any values in it (all empty fields, all full fields, with entries or no entries, presaved locally or not) we always get the same result. First, the system hangs for a couple seconds or even minutes: Then the system throws and error: At this point I decide to check the logs. TLex error log only saves this: LOAD ERROR REPORT: "C:\Users\perro\Documents\TLex\ErrorReports\Load error report (Lexicografia_tl_) (2023-01-14 03h23).txt" I activated the MySQL logs, and in any try, with any values in it, it always throws the following: 2023-01-16T19:33:41.216616Z??????? 44 Connect tlex at XXX.XXX.XXX.XX on lexicografia using SSL/TLS 2023-01-16T19:33:41.395388Z??????? 44 Query???? SET NAMES utf8mb4 2023-01-16T19:33:41.573590Z??????? 44 Query???? SET character_set_results = NULL 2023-01-16T19:33:41.757360Z??????? 44 Query???? SET SQL_AUTO_IS_NULL = 0 2023-01-16T19:33:41.945809Z??????? 44 Query???? SET AUTOCOMMIT=0 2023-01-16T19:33:42.270723Z??????? 38 Query???? set @@sql_select_limit=DEFAULT 2023-01-16T19:33:42.460951Z??????? 38 Query???? SELECT TABLE_NAME,TABLE_COMMENT,IF(TABLE_TYPE='BASE TABLE', 'TABLE', TABLE_TYPE),TABLE_SCHEMA FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA=DATABASE() AND ( TABLE_TYPE='BASE TABLE' OR TABLE_TYPE='VIEW' ) AND TABLE_NAME LIKE 'tl_document' ORDER BY TABLE_SCHEMA, TABLE_NAME 2023-01-16T19:33:42.651017Z??????? 38 Prepare?? INSERT INTO tl_document (node_id,name,description,createdby,copyright,url,schema_version,mediapath) VALUES (?,?,?,?,?,?,?,?) 2023-01-16T19:33:42.830815Z??????? 38 Query???? SELECT TABLE_NAME,TABLE_COMMENT,IF(TABLE_TYPE='BASE TABLE', 'TABLE', TABLE_TYPE),TABLE_SCHEMA FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA=DATABASE() AND ( TABLE_TYPE='BASE TABLE' OR TABLE_TYPE='VIEW' ) AND TABLE_NAME LIKE 'tl_document' ORDER BY TABLE_SCHEMA, TABLE_NAME 2023-01-16T19:33:43.016648Z??????? 38 Query???? SELECT node_id,name,description,createdby,copyright,url,schema_version,mediapath FROM tl_document 2023-01-16T19:33:43.200718Z??????? 38 Query???? CREATE TABLE tl_blocks (sortorder integer,guid varchar(1000),number integer,name varchar(1000),size integer,data varchar(1000)) 2023-01-16T19:33:43.549805Z??????? 38 Query ROLLBACK 2023-01-16T19:33:45.730791Z??????? 38 Query???? UPDATE tl_users SET loggedin = '0'?? WHERE user_id = '1' 2023-01-16T19:33:45.920780Z??????? 38 Query???? SELECT Now() 2023-01-16T19:33:46.092584Z??????? 38 Query COMMIT 2023-01-16T19:33:46.257757Z??????? 38 Query COMMIT 2023-01-16T19:33:46.450663Z??????? 38 Close stmt Finally, the tl_document table shows this: mysql> select * from tl_document; +---------+------+-------------+-----------+-----------+------+--------------------+-----------+ | node_id | name | description | createdby | copyright | url | schema_version???? | mediapath | +---------+------+-------------+-----------+-----------+------+--------------------+-----------+ |?????? 1 | Test |???????????? |?????????? |?????????? | | 3.0999999046325684 |?????????? | +---------+------+-------------+-----------+-----------+------+--------------------+-----------+ So at this point we don't know what we are doing wrong. So we would appreciate some hints on how we can make TLex MySQL connection work and, therefore, evaluate if we can use TLex for our needs. Thanks, Ram -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 1_test.JPG Type: image/jpeg Size: 11967 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 3_not_responding.JPG Type: image/jpeg Size: 16294 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 8_failed.JPG Type: image/jpeg Size: 17287 bytes Desc: not available URL: