CL-DBI throws EXCEPTION_ACCESS_VIOLATION when used with MYSQL database query with multiple columns

[pawandeshpande]

CL-DBI throws EXCEPTION_ACCESS_VIOLATION when used with MYSQL database query with multiple columns

[fukamachi]

Cannot reproduce it.
It may depend on the data in "crm_users" table or the difference of character encodings between MySQL and SBCL.

[pawandeshpande]

How should I set the character encodings between MYSQL and SBCL? I also tried

"set names utf8" query from SBCL. Did not help.

[fukamachi]

Are all data in "crm_users" UTF-8 or ASCII strings?

[pawandeshpande]

Hi Eitaro,

The data I have inserted is in ASCII strings.

thanks
Pawan.

On Thu, Jan 7, 2016 at 11:06 PM, Eitaro Fukamachi [email protected]
wrote:

Are all data in "crm_users" UTF-8 or ASCII strings?

—
Reply to this email directly or view it on GitHub
#25 (comment).

[pawandeshpande]

I have queried the Mysql database for collation and here are the results.

mysql> show variables like 'collation%';
+----------------------+-----------------+
| Variable_name | Value |
+----------------------+-----------------+
| collation_connection | utf8_general_ci |
| collation_database | utf8_general_ci |
| collation_server | utf8_general_ci |
+----------------------+-----------------+
3 rows in set (0.00 sec)

I also ran the query "set names utf8". After that I ran the following query

mysql> show variables like 'character_set%';
+--------------------------+----------------------------------------------------
-----+
| Variable_name | Value
|
+--------------------------+----------------------------------------------------
-----+
| character_set_client | utf8
|
| character_set_connection | utf8
|
| character_set_database | utf8
|
| character_set_filesystem | binary
|
| character_set_results | utf8
|
| character_set_server | utf8
|
| character_set_system | utf8
|
| character_sets_dir | C:\Program Files\MySQL\MySQL Server 5.6\share\chars
ets\ |
+--------------------------+----------------------------------------------------
-----+
8 rows in set (0.00 sec)

Still I am getting the same results.

[RetainCountZero]

I have the same issue here. Windows 10 x64, SBCL 1.3.9 x64, MySQL Connector C x64 6.1.6.

I needed the "SET names 'utf8';" command at first to access varchar field correctly.
Then, running a SELECT with a single column worked. Next I wanted to query simple integer columns:

(cl-mysql::query "SELECT bug_id FROM bugs WHERE bug_id = 182222")
=> ((((182222)) (("bug_id" :INT24 49667))))

(cl-mysql::query "SELECT assigned_to FROM bugs WHERE bug_id = 182222")
=> ((((2507)) (("assigned_to" :INT24 52257))))

Combining both columns into a single query:
(cl-mysql::query "SELECT bug_id, assigned_to FROM bugs WHERE bug_id = 182222")
=> EXCEPTION_ACCESS_VIOLATION

Both fields are of type "mediumint(9)" in the database. Perhaps this helps, because I think it's not just a question of different encodings between CL and the database.

[RetainCountZero]

I tried the same with CCL 1.11 x86 (32-bit). This combination works.

Looks like it's a 64-bit issue, while 32-bit (ccl, mysql-connector-c) on Windows 10 x64 works.