#[repr(C)]pub struct NET {Show 27 fields
pub vio: *mut Vio,
pub buff: *mut c_uchar,
pub buff_end: *mut c_uchar,
pub write_pos: *mut c_uchar,
pub read_pos: *mut c_uchar,
pub fd: my_socket,
pub remain_in_buf: c_ulong,
pub length: c_ulong,
pub buf_length: c_ulong,
pub where_b: c_ulong,
pub max_packet: c_ulong,
pub max_packet_size: c_ulong,
pub pkt_nr: c_uint,
pub compress_pkt_nr: c_uint,
pub write_timeout: c_uint,
pub read_timeout: c_uint,
pub retry_count: c_uint,
pub fcntl: c_int,
pub return_status: *mut c_uint,
pub reading_or_writing: c_uchar,
pub save_char: c_uchar,
pub compress: bool,
pub last_errno: c_uint,
pub error: c_uchar,
pub last_error: [c_char; 512],
pub sqlstate: [c_char; 6],
pub extension: *mut c_void,
}Fields§
§vio: *mut Vio§buff: *mut c_uchar§buff_end: *mut c_uchar§write_pos: *mut c_uchar§read_pos: *mut c_uchar§fd: my_socket§remain_in_buf: c_ulongSet if we are doing several queries in one command ( as in LOAD TABLE … FROM MASTER ), and do not want to confuse the client with OK at the wrong time
length: c_ulongSet if we are doing several queries in one command ( as in LOAD TABLE … FROM MASTER ), and do not want to confuse the client with OK at the wrong time
buf_length: c_ulongSet if we are doing several queries in one command ( as in LOAD TABLE … FROM MASTER ), and do not want to confuse the client with OK at the wrong time
where_b: c_ulongSet if we are doing several queries in one command ( as in LOAD TABLE … FROM MASTER ), and do not want to confuse the client with OK at the wrong time
max_packet: c_ulong§max_packet_size: c_ulong§pkt_nr: c_uint§compress_pkt_nr: c_uint§write_timeout: c_uint§read_timeout: c_uint§retry_count: c_uint§fcntl: c_int§return_status: *mut c_uint§reading_or_writing: c_uchar§save_char: c_uchar§compress: bool§last_errno: c_uint§error: c_uchar§last_error: [c_char; 512]Client library error message buffer. Actually belongs to struct MYSQL.
sqlstate: [c_char; 6]Client library sqlstate buffer. Set along with the error message.
extension: *mut c_voidExtension pointer, for the caller private use. Any program linking with the networking library can use this pointer, which is handy when private connection specific data needs to be maintained. The mysqld server process uses this pointer internally, to maintain the server internal instrumentation for the connection.