Xbasic won't insert or update MySQL: "The data type returned by your database is not recognized."

[jchasko]

A Xbasic text import utility throws the error above, on every line following the 63rd line of the 30K line import.
If I move that line to the front the text file, it still stops on the (different) 63rd line, and every one thereafter.
So, it is not the content. The import had been working like a top for months, and I can't see what recent work could apply.

The content of the line is irrelevant, but this is a typical SQL

INSERT INTO PRICE (brand,model,displaysize,full_description,retail_price,sale_sort,product_id,model_compact,sell_url,pixel,image_url,brand_compact,part_number,grade,concat_size,extraload,loadrange,lt,speed,m_s,run_flat,warranty_miles,utqgwear,utqgtraction,idsku,tg_modelid,long_benefit,image_54p,image_200p,image_400p,image_800p,done,seller_type,idseller) VALUES (:brand,:model,:displaysize,:full_description,:retail_price,:sale_sort,:product_id,:model_compact,:sell_url,:pixel,:image_url,:brand_compact,:part_number,:grade,:concat_size,:extraload,:loadrange,:lt,:speed,:m_s,:run_flat,:warranty_miles,:utqgwear,:utqgtraction,:idsku,:tg_modelid,:long_benefit,:image_54p,:image_200p,:image_400p,:image_800p,:done,:seller_type,:idseller)

The arguments:
Arg brand=Bridgestone
Arg model=Potenza Sport
Arg displaysize=305/30-20
Arg full_description=Bridgestone Potenza Sport 305/30-20 XL (103Y) Max Performance Summer
Arg retail_price=485.99
Arg sale_sort=485.99
Arg product_id=03YR0PSXL
Arg model_compact=PotenzaSport
Arg sell_url=https://www.dpbolvw.net/click-100393843-13697786?url=https%3A%2F%2Fwww.tirerack.com%2Ftires%2Ftires.jsp%3FtireMake%3DBridgestone%26tireModel%3DPotenza+Sport%26partnum%3D03YR0PSXL%26GCID%3DC13674x012-tire%26KEYWORD%3Dtires.jsp_Bridgestone_Potenza+Sport_Tire%26code%3Dyes
Arg pixel=https://www.lduhtrp.net/image-100393843-13697786
Arg image_url=https://www.tirerack.com/content/dam/tires/bridgestone/bs_potenza_sport_full.jpg
Arg brand_compact=Bridgestone
Arg part_number=008146
Arg grade=1
Arg concat_size=305-30-20
Arg extraload=
Arg loadrange=
Arg lt=Y
Arg speed=S
Arg m_s=N
Arg run_flat=N
Arg warranty_miles=55,000
Arg utqgwear=540
Arg utqgtraction=A
Arg idsku=3822
Arg tg_modelid=17546
Arg long_benefit= Next generation ultrahigh silica compount. 3D sipe technology. Specially engineered pattern geometry. Tuned tread sequencing. provides confident grip and handling in wet and dry conditions. optimizes pattern stiffness for a balance of traction and wear performance. helps maintain contact pressure and promotes water evacuation for improved wet performance. minimizes pattern noise, promoting a quiet, comfortable ride.
Arg image_54p=
Arg image_200p=
Arg image_400p=
Arg image_800p=
Arg done=1
Arg seller_type=W
Arg idseller=9

[lgrupido]

So you are importing data by reading the file, then doing a sql insert one row at a time, yes?

Have you updated Alpha? (If so, what happens if you go back to the version you on were before.)

I wonder if you are having a memory issue. Have you tried restarting everything, including the server? On a completely fresh restart, does it get any further?

If you import a file that only has 62 rows, does it work properly?

What happens if you cut the file size in half before importing?

Is there a number of starting records (maybe 100 rows?) that actually works without crashing?

What does the 62nd record look like? Is there anything different comparing the two?

Is there a way you could stop the import after 50 rows, then start it again, only the second time import rows 51-100? and so on in a loop?

(The point would be to close the connection and reopen it in between each run to free up memory.)

[jchasko]

Those are great questions. The problem just fixed itself, perhaps from rebooting? That could have been memory. I did restart the Alpha app, because running heavy utility stuff in the app can (rarely) break it, but that didn't help. The mariadb is in the cloud, so I guess the reboot. I chalk it up to WTF, and to Windows being a steaming pile. :)