Query-based insertion or updating of BLOB values is not supported.-- ????

am 11.05.2007 04:24:43 von Jordan Bradford

One of our clients has data on their internal SQL Server which they will
be sending to our webserver periodically using the MySQL ODBC driver. In
the testing we've done so far we've had problems with large character
fields.

In MySQL the problem columns are defined as type TEXT, which is reported
to SQL Server as a LONG VARCHAR. On their end these columns are defined
as nvarchar(2000).

Any INSERTs they attempt to have their system perform on our MySQL
server using data from one of those columns gives them this error:

"Query-based insertion or updating of BLOB values is not supported."

What do we need to do to make this work?

Thank you,

-- Jordan Bradford
----------------------------
BrownBoots Interactive, Inc.
108 South Main St.
Fond du Lac, WI 54935
920-906-9175
http://www.brownboots.com/

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

Re: Query-based insertion or updating of BLOB values is not supported. -- ????

am 11.05.2007 23:19:31 von Jess Balint

On Thu, May 10, 2007 at 09:24:43PM -0500, Jordan Bradford wrote:
> One of our clients has data on their internal SQL Server which they will
> be sending to our webserver periodically using the MySQL ODBC driver. In
> the testing we've done so far we've had problems with large character
> fields.
>
> In MySQL the problem columns are defined as type TEXT, which is reported
> to SQL Server as a LONG VARCHAR. On their end these columns are defined
> as nvarchar(2000).
>
> Any INSERTs they attempt to have their system perform on our MySQL
> server using data from one of those columns gives them this error:
>
> "Query-based insertion or updating of BLOB values is not supported."

I'm not sure exactly what would cause this, but have you tried enabling
the "Don't optimize column width" option on the MySQL DSN?

It seems to have worked as mentioned in this bug report:
http://bugs.mysql.com/bug.php?id=12446

Jess

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

Re: Query-based insertion or updating of BLOB values is not supported.-- ????

am 14.05.2007 16:12:08 von Jordan Bradford

Yes, that option was checked.

I had them send me a list of all the options and their current settings:

Connect Options tab:
- Port BLANK
- Socket BLANK
- Initial Statement BLANK

Advanced tab:
Flags 1 tab:
- Don't Optimize Column Width CHECKED
- Return Matching Rows UNCHECKED
- Allow Big Results CHECKED
- Use Compressed Protocol UNCHECKED
- Change BIGINT Columns To Int UNCHECKED
- Safe UNCHECKED
- Enable Auto Reconnect UNCHECKED
- Enable auto_increment NULL search UNCHECKED
Flags 2 tab:
- Don't Prompt Upon Connect UNCHECKED
- Enable Dynamic Cursor UNCHECKED
- Ingore # In Table Name UNCHECKED
- Use Manager Cursors UNCHECKED
- Don't Use Set Locale UNCHECKED
- Pad Char To Full Length UNCHECKED
- Don't Cache Result (forward only cursors) UNCHECKED
Flags 3 tab:
- Return Table Names For SQLDescribeCol UNCHECKED
- Ignore Space After Function Names UNCHECKED
- Force Use Of Named Pipes UNCHECKED
- No Catalog (exp) UNCHECKED
- Read Options From my.cnf UNCHECKED
- Disable Transactions UNCHECKED
- Force Use Of Forward Only Cursors UNCHECKED
Debug:
- Trace Driver Calls To myodbc.log UNCHECKED
- Save Queries to myodbc.sql UNCHECKED

Nothing is checked except "Don't Optimize Column Widths" and "Allow Big
Results."

-- Jordan Bradford
----------------------------
BrownBoots Interactive, Inc.
108 South Main St.
Fond du Lac, WI 54935
920-906-9175
http://www.brownboots.com/

Jess Balint wrote:
> On Thu, May 10, 2007 at 09:24:43PM -0500, Jordan Bradford wrote:
>> One of our clients has data on their internal SQL Server which they will
>> be sending to our webserver periodically using the MySQL ODBC driver. In
>> the testing we've done so far we've had problems with large character
>> fields.
>>
>> In MySQL the problem columns are defined as type TEXT, which is reported
>> to SQL Server as a LONG VARCHAR. On their end these columns are defined
>> as nvarchar(2000).
>>
>> Any INSERTs they attempt to have their system perform on our MySQL
>> server using data from one of those columns gives them this error:
>>
>> "Query-based insertion or updating of BLOB values is not supported."
>
> I'm not sure exactly what would cause this, but have you tried enabling
> the "Don't optimize column width" option on the MySQL DSN?
>
> It seems to have worked as mentioned in this bug report:
> http://bugs.mysql.com/bug.php?id=12446
>
> Jess
>

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org

Re: Query-based insertion or updating of BLOB values is not supported.-- ????

am 14.05.2007 16:12:26 von Jordan Bradford