DBImport V3.1 updated and released CYQ. DBImport database reverse engineering and bulk import database tool V2.0 [added batch Export Database scripts and database design documents]

After another year, I finally updated the version. However, this version only advances to a small bit, from 3.0 to 3.1.

 

The version number is small, which indicates that this change is not big, but let's talk about it:1: The latest CYQ. Data V5 series with better performance have been replaced, and the Data batch insertion speed has been improved.
2: Modify the image type and time type conversion of MySql.
3: Modify the table structure of Txt and Xml.
4: The error output is automatically recorded in the Logs folder under the directory.
5: If the paging stored procedure is integrated with MSSQL and ORAcle, the paging process is automatically created without having to be created in advance.

6: the page has been changed to less text:

 

: Http://www.cyqdata.com/download/article-detail-42517

Because they are all IT people, this simple operation will not be taught step by step. IT is a small CASE for everyone's emotional intelligence, interface operations.

For more information, see CYQ. DBImport database reverse engineering and batch import database tool V2.0. [add batch Export Database scripts and database design documents]

 

In addition, add the following technical issues:

Problem:
Some netizens reported that the time field was missing when MySql guided Sqlite.
After local testing, we found that it was indeed gone.
After multi-party verification, we found that the time field exists in mysql and is not available in other databases. Therefore, this is generally not used in cross-database design.
But when people use it, they have to deal with it.

Questions and answers:

During this test, an error was reported when the field time was inserted: MySql: Only TimeSpan objects can be serialized by MySqlTimeSpan
This error was found on the Internet. It can be seen that the time field is rarely used.
In the past, the default method was to use the conventional method. The corresponding type of parameter passing via parameterization was DbType. Time. I didn't expect Microsoft to dig a hole and jump up, So I reported the above error.
Finally, I added a judgment and changed it to DbType. String to survive.

I know everyone's taste. I have provided a picture: