The Ultimate Guide to High Availability with MariaDB

Comments - MariaDB ODBC Driver 0.9.1 Release Notes

9 years, 8 months ago JD Austin
Re: MariaDB ODBC Driver 0.9.1 Release Notes

I've successfully used an ODBC tool to query the data to verify credentials; I'm hoping to get our company to go with MariaDB rather than SQL Server and this interoperability test isn't going so well. I'm hoping you can throw me a clue.

Is there a way to successfully query from MariaDB an ODBC data source to create or insert into a table from within the mysql command line? The odbc table (Filemaker Server) has varchar(1000000) columns; I tried creating a table with the maximum varchar size but the data is too big to fit: 

create table Motions (
  MotionsNo INT NOT NULL,
  BoardMeeting date,
  Motion varchar(21845),
  Reference varchar(21845))
engine=connect table_type=ODBC block_size=10 tabname='Motions' Connection='DSN=Motions;Uid=gbmotions;Pwd=<thepassword>;';
ERROR 1118 (42000): Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

If I try text fields like I normally would I get an error that the connect engine doesn't support BLOB/TEXT columns:

create table Motions (
  MotionsNo INT NOT NULL,
  BoardMeeting date,
  Motion TEXT,
  Reference TEXT)
engine=connect table_type=ODBC block_size=10 tabname='Motions' Connection='DSN=Motions;Uid=gbmotions;Pwd=<thepassword>;';
ERROR 1163 (42000): Storage engine CONNECT doesn't support BLOB/TEXT columns

Is there a way around this issue?

 
9 years, 8 months ago Ian Gilfillan
Re: MariaDB ODBC Driver 0.9.1 Release Notes

The connect_type_conv system variable can be changed from it's default setting to accept TEXT fields, but this won't help you in your case, as it converts to a VARCHAR, which won't work. See CONNECT data type conversion. So no, not that I'm aware.

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.