OK, I figured out what was going on. When I created a varchar(256) in the MySQL destination table, MySQL silently converted to it text (instead of protesting that varchar maxes out at 255), and I just found the problem by executing "show create table MyTable".
--- "Homam S.A." <[EMAIL PROTECTED]> wrote: > I have a simple table in SQL Server that doesn't > have > any BLOB field (no text or image columns). Only > char, > varchar, bit, and int columns. I created a DTS > package > that uses a simple select to copy the contents of > this > table into an identical table created in MySQL > through > MyODBC 3.51. > > Whenver I execute this package, I get this weird > error: > > "Query-based insertion or updating of BLOB values is > not supported" > > But like I said above, I'm not using any BLOB column > neither on the source SQL Server table nor on the > destination MySQL table. > > I searched for this problem on the Internet and all > I > got was people having the same the problem with no > answer other than more poeple looking for a > solution. > > Any ideas about this problem? Does MySQL work with > DTS, or I have to revert to dump files? > > I apprecaite your help, > > Homam > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - Helps protect you from nasty viruses. > http://promotions.yahoo.com/new_mail > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
