Forum Replies Created
-
AuthorPosts
-
JasonRMemberpeterlaursen wrote on Jun 29 2007, 03:06 PM:It is the ODBC driver that returns 'SQL_TYPE_TIMESTAMP' for the datatype.
There will always be issues with such datatypes that are not identical on different systems!
We have described the issue here:
http://webyog.com/faq/17_125_en.html
I think we chose the best option!
Hi Thanks for the info.
I understand, and agree that timestamp is normally the best option. And was not suggesting that it be changed as the default.
I was just simply wondering if there was a way of changing this behavior temporarily. But that is fine, I will manually change the column mappings for the tables / columns that it effects.
Thanks for taking the time to respond.
Cheers,
Jason
JasonRMemberRohit wrote on Jun 22 2007, 02:54 AM:Can you try 6.03? We have actually fixed a blog issue recently.THANK YOU! 6.03 worked. I still need to double check the results, but the data does not have the 0000 though out the file.
I had only download the the software last week, so did not think to check for an update.
Thanks again.
Cheers,
Jason
JasonRMemberpeterlaursen wrote on Jun 21 2007, 06:58 PM:“Some data that is stored in sql server as type “image” that get mapped to a longblob in MySQL is damaged. The data is a pdf file.”Ok .. we will have to check this with the SQL server 'image' type.
Do you mean to tell that the data on SQL Server is PDF?
Will they migrate OK if stored in a SQL server 'plain' BLOB type?
please also tell:
SQLserver version?
ODBC driver version?
Hi thanks for the reply.
In SQL Server, type “image” is a blob. So the only way to store a blob in SQL Server is via the image type.
The data that is in the blob is a pdf.
I have attached a create table script for both SQL Server and MySQL.
As you can see from the script there are several blob columns in the table. The only one that seems to be an issue is the combinedStatmentPdf column. The other blob columns the data appears to have been copied correctly.
SQL Server 2000, version 8.00.194
MySQL ODBC driver version 3.51 (3.51.12.0)
SQL Server ODBC driver version 2000.85.1117.00
I appreciate you taking the time to look into this.
Cheers,
Jason
-
AuthorPosts