非常棒的数据迁移工具，支持mysql，mssql

<?xml version="1.0"?> <doc> <assembly> <name>Npgsql</name> </assembly> <members> <member name="T:Npgsql.BackendMessages.CopyDataMessage"> <summary> Note that this message doesn't actually contain the data, but only the length. Data is processed directly from the connector's buffer. </summary> </member> <member name="T:Npgsql.BackendMessages.CopyDoneMessage"> <remarks> Note: This message is both a frontend and a backend message </remarks> </member> <member name="T:Npgsql.BackendMessages.DataRowMessage"> <summary> DataRow is special in that it does not parse the actual contents of the backend message, because in sequential mode the message will be traversed and processed sequentially by <see cref="T:Npgsql.NpgsqlSequentialDataReader"/>. </summary> </member> <member name="T:Npgsql.BackendMessages.ErrorOrNoticeMessage.ErrorFieldTypeCode"> <summary> Error and notice message field codes </summary> </member> <member name="T:Npgsql.BackendMessages.RowDescriptionMessage"> <summary> A RowDescription message sent from the backend. </summary> <remarks> See http://www.postgresql.org/docs/current/static/protocol-message-formats.html </remarks> </member> <member name="M:Npgsql.BackendMessages.RowDescriptionMessage.GetFieldIndex(System.String)"> <summary> Given a string name, returns the field's ordinal index in the row. </summary> </member> <member name="M:Npgsql.BackendMessages.RowDescriptionMessage.TryGetFieldIndex(System.String,System.Int32@)"> <summary> Given a string name, returns the field's ordinal index in the row. </summary> </member> <member name="T:Npgsql.BackendMessages.RowDescriptionMessage.InsensitiveComparer"> <summary> Comparer that's case-insensitive and Kana width-insensitive </summary> </member> <member name="T:Npgsql.BackendMessages.FieldDescription"> <summary> A descriptive record on a single field received from PostgreSQL. See RowDescription in http://www.postgresql.org/docs/current/static/protocol-message-formats.html </summary> </member> <member name="P:Npgsql.BackendMessages.FieldDescription.Name"> <summary> The field name. </summary> </member> <member name="P:Npgsql.BackendMessages.FieldDescription.TypeOID"> <summary> The object ID of the field's data type. </summary> </member> <member name="P:Npgsql.BackendMessages.FieldDescription.TypeSize"> <summary> The data type size (see pg_type.typlen). Note that negative values denote variable-width types. </summary> </member> <member name="P:Npgsql.BackendMessages.FieldDescription.TypeModifier"> <summary> The type modifier (see pg_attribute.atttypmod). The meaning of the modifier is type-specific. </summary> </member> <member name="P:Npgsql.BackendMessages.FieldDescription.TableOID"> <summary> If the field can be identified as a column of a specific table, the object ID of the table; otherwise zero. </summary> </member> <member name="P:Npgsql.BackendMessages.FieldDescription.ColumnAttributeNumber"> <summary> If the field can be identified as a column of a specific table, the attribute number of the column; otherwise zero. </summary> </member> <member name="P:Npgsql.BackendMessages.FieldDescription.FormatCode"> <summary> The format code being used for the field. Currently will be zero (text) or one (binary). In a RowDescription returned from the statement variant of Describe, the format code is not yet known and will always be zero. </summary> </member> <member name="P:Npgsql.BackendMessages.FieldDescription.Handler"> <summary> The Npgsql type handler assigned to handle this field. Returns <see cref="T:Npgsql.TypeHandlers.UnknownTypeHandler"/> for fields with format text. </summary> </member> <member name="P:Npgsql.BackendMessages.FieldDescription.RealHandler"> <summary> The type handler resolved for this field, regardless of whether it's binary or text. </summary> </member> <member name="M:Npgsql.BackendMessages.FieldDescription.ToString"> <summary> Returns a string that represents the current object. </summary> </member> <member name="T:Npgsql.IBackendMessage"> <summary> Base class for all classes which represent a message sent by the PostgreSQL backend. </summary> </member> <member name="T:Npgsql.FrontendMessage"> <summary> Base class for all classes which represent a message sent to the PostgreSQL backend. Concrete classes which directly inherit this represent arbitrary-length messages which can chunked. </summary> </member> <member name="M:Npgsql.FrontendMessage.Write(Npgsql.NpgsqlWriteBuffer,System.Boolean)"> <param name="buf">the buffer into which to write the message.</param> <param name="async"></param> <returns> Whether there was enough space in the buffer to contain the entire message. If false, the buffer should be flushed and write should be called again. </returns> </member> <member name="P:Npgsql.FrontendMessage.ResponseMessageCount"> <summary> Returns how many messages PostgreSQL is expected to send in response to this message. Used for message prepending. </summary> </member> <member name="T:Npgsql.SimpleFrontendMessage"> <summary> Represents a simple frontend message which is typically small and fits well within the write buffer. The message is first queries for the number of bytes it requires, and then writes itself out. </summary> </member> <member name="P:Npgsql.SimpleFrontendMessage.Length"> <summary> Returns the number of bytes needed to write this message. </summary> </member> <member name="M:Npgsql.SimpleFrontendMessage.WriteFully(Npgsql.NpgsqlWriteBuffer)"> <summary> Writes the message contents into the buffer. </summary> </member> <member name="T:Npgsql.StatementType"> <summary> Specifies the type of SQL statement, e.g. SELECT </summary> </member> <member name="T:Npgsql.ConnectorPool"> <summary> Connection pool for PostgreSQL physical connections. Attempts to allocate connections over MaxPoolSize will block until someone releases. Implementation is completely lock-free to avoid contention, and ensure FIFO for open attempts waiting (because the pool is at capacity). </summary> </member> <member name="P:Npgsql.ConnectorPool.UserFacingConnectionString"> <summary> Contains the connection string returned to th