1. When exporting SQL files using PowerDesigner (with export steps):
(1) First switch the database, for example, in MySQL:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/6D/DC/wKiom1VtaAeBwKdbAAHV7EfGPYo271.jpg "title=" 00001. PNG "alt=" wkiom1vtaaebwkdbaahv7efgpyo271.jpg "/>
(2) Start generating SQL, as shown in, Save as SQL file:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/6D/D7/wKioL1VtahaisEzlAAHS0Ye8R-A723.jpg "title=" 00002. PNG "alt=" wkiol1vtahaisezlaahs0ye8r-a723.jpg "/>650) this.width=650; src=" http://s3.51cto.com/wyfs02/M01/6D/D7 /wkiol1vtaieaanctaaklrzgi204623.jpg "title=" 00003.png "alt=" Wkiol1vtaieaanctaaklrzgi204623.jpg "/>
(3) When you find that the exported SQL does not have a comment, add the comment column by method:
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/6D/DC/wKiom1VtaQeSpb5LAASnqVTJ-Tg984.jpg "title=" 001. PNG "alt=" wkiom1vtaqespb5laasnqvtj-tg984.jpg "/>
(4) and then the first two steps to export, at this point, export problem resolution;
2. When importing SQL files using the MySQL client:
(1) because the file encoding format saved by the default of PD is ANSI, and after importing SQL in this format, it is found that the comment was not successfully imported;
(2) It is natural to modify the code when the response, then open the Save as UTF-8 format with Notepad, this thought to succeed, but not finished, at this time when the import will occur grammar and other errors;
(3) because the encoding format in Notepad is limited, with the help of the EditPlus tool, it is found that there will be a number of different encoding format, and after Notepad saved as the UTF-8 format file, in fact: UTF-8 + BOM encoding; To find the cause of the problem, save as UTF-8 to solve the import problem ;
This article is from the "Pig Flying" blog, please be sure to keep this source http://jiyanle.blog.51cto.com/6932197/1657571
Considerations for PD exporting SQL and MySQL clients when importing SQL files