Rechercher dans le manuel MySQL
28.7.9 C API Prepared Statement Data Structures
[+/-]
Prepared statements use several data structures:
To obtain a statement handler, pass a
MYSQL
connection handler tomysql_stmt_init()
, which returns a pointer to aMYSQL_STMT
data structure. This structure is used for further operations with the statement. To specify the statement to prepare, pass theMYSQL_STMT
pointer and the statement string tomysql_stmt_prepare()
.To provide input parameters for a prepared statement, set up
MYSQL_BIND
structures and pass them tomysql_stmt_bind_param()
. To receive output column values, set upMYSQL_BIND
structures and pass them tomysql_stmt_bind_result()
.The
MYSQL_TIME
structure is used to transfer temporal data in both directions.
The following discussion describes the prepared statement data types in detail. For examples that show how to use them, see Section 28.7.11.10, “mysql_stmt_execute()”, and Section 28.7.11.11, “mysql_stmt_fetch()”.
This structure is a handler for a prepared statement. A handler is created by calling
mysql_stmt_init()
, which returns a pointer to aMYSQL_STMT
. The handler is used for all subsequent operations with the statement until you close it withmysql_stmt_close()
, at which point the handler becomes invalid and should no longer be used.The
MYSQL_STMT
structure has no members intended for application use. Applications should not try to copy aMYSQL_STMT
structure. There is no guarantee that such a copy will be usable.Multiple statement handlers can be associated with a single connection. The limit on the number of handlers depends on the available system resources.
This structure is used both for statement input (data values sent to the server) and output (result values returned from the server):
For input, use
MYSQL_BIND
structures withmysql_stmt_bind_param()
to bind parameter data values to buffers for use bymysql_stmt_execute()
.For output, use
MYSQL_BIND
structures withmysql_stmt_bind_result()
to bind buffers to result set columns, for use in fetching rows withmysql_stmt_fetch()
.
To use a
MYSQL_BIND
structure, zero its contents to initialize it, then set its members appropriately. For example, to declare and initialize an array of threeMYSQL_BIND
structures, use this code:MYSQL_BIND bind[3]; memset(bind, 0, sizeof(bind));
The
MYSQL_BIND
structure contains the following members for use by application programs. For several of the members, the manner of use depends on whether the structure is used for input or output.enum enum_field_types buffer_type
The type of the buffer. This member indicates the data type of the C language variable bound to a statement parameter or result set column. For input,
buffer_type
indicates the type of the variable containing the value to be sent to the server. For output, it indicates the type of the variable into which a value received from the server should be stored. For permissiblebuffer_type
values, see Section 28.7.9.1, “C API Prepared Statement Type Codes”.void *buffer
A pointer to the buffer to be used for data transfer. This is the address of a C language variable.
For input,
buffer
is a pointer to the variable in which you store the data value for a statement parameter. When you callmysql_stmt_execute()
, MySQL use the value stored in the variable in place of the corresponding parameter marker in the statement (specified with?
in the statement string).For output,
buffer
is a pointer to the variable in which to return a result set column value. When you callmysql_stmt_fetch()
, MySQL stores a column value from the current row of the result set in this variable. You can access the value when the call returns.To minimize the need for MySQL to perform type conversions between C language values on the client side and SQL values on the server side, use C variables that have types similar to those of the corresponding SQL values:
For numeric data types,
buffer
should point to a variable of the proper numeric C type. For integer variables (which can bechar
for single-byte values or an integer type for larger values), you should also indicate whether the variable has theunsigned
attribute by setting theis_unsigned
member, described later.For character (nonbinary) and binary string data types,
buffer
should point to a character buffer.For date and time data types,
buffer
should point to aMYSQL_TIME
structure.
For guidelines about mapping between C types and SQL types and notes about type conversions, see Section 28.7.9.1, “C API Prepared Statement Type Codes”, and Section 28.7.9.2, “C API Prepared Statement Type Conversions”.
unsigned long buffer_length
The actual size of
*buffer
in bytes. This indicates the maximum amount of data that can be stored in the buffer. For character and binary C data, thebuffer_length
value specifies the length of*buffer
when used withmysql_stmt_bind_param()
to specify input values, or the maximum number of output data bytes that can be fetched into the buffer when used withmysql_stmt_bind_result()
.unsigned long *length
A pointer to an
unsigned long
variable that indicates the actual number of bytes of data stored in*buffer
.length
is used for character or binary C data.For input parameter data binding, set
*length
to indicate the actual length of the parameter value stored in*buffer
. This is used bymysql_stmt_execute()
.For output value binding, MySQL sets
*length
when you callmysql_stmt_fetch()
. Themysql_stmt_fetch()
return value determines how to interpret the length:If the return value is 0,
*length
indicates the actual length of the parameter value.If the return value is
MYSQL_DATA_TRUNCATED
,*length
indicates the nontruncated length of the parameter value. In this case, the minimum of*length
andbuffer_length
indicates the actual length of the value.
length
is ignored for numeric and temporal data types because thebuffer_type
value determines the length of the data value.If you must determine the length of a returned value before fetching it, see Section 28.7.11.11, “mysql_stmt_fetch()”, for some strategies.
bool *is_null
This member points to a
bool
variable that is true if a value isNULL
, false if it is notNULL
. For input, set*is_null
to true to indicate that you are passing aNULL
value as a statement parameter.is_null
is a pointer to a boolean scalar, not a boolean scalar, to provide flexibility in how you specifyNULL
values:If your data values are always
NULL
, useMYSQL_TYPE_NULL
as thebuffer_type
value when you bind the column. The otherMYSQL_BIND
members, includingis_null
, do not matter.If your data values are always
NOT NULL
, setis_null = (bool*) 0
, and set the other members appropriately for the variable you are binding.In all other cases, set the other members appropriately and set
is_null
to the address of abool
variable. Set that variable's value to true or false appropriately between executions to indicate whether the corresponding data value isNULL
orNOT NULL
, respectively.
For output, when you fetch a row, MySQL sets the value pointed to by
is_null
to true or false according to whether the result set column value returned from the statement is or is notNULL
.bool is_unsigned
This member applies for C variables with data types that can be
unsigned
(char
,short int
,int
,long long int
). Setis_unsigned
to true if the variable pointed to bybuffer
isunsigned
and false otherwise. For example, if you bind asigned char
variable tobuffer
, specify a type code ofMYSQL_TYPE_TINY
and setis_unsigned
to false. If you bind anunsigned char
instead, the type code is the same butis_unsigned
should be true. (Forchar
, it is not defined whether it is signed or unsigned, so it is best to be explicit about signedness by usingsigned char
orunsigned char
.)is_unsigned
applies only to the C language variable on the client side. It indicates nothing about the signedness of the corresponding SQL value on the server side. For example, if you use anint
variable to supply a value for aBIGINT UNSIGNED
column,is_unsigned
should be false becauseint
is a signed type. If you use anunsigned int
variable to supply a value for aBIGINT
column,is_unsigned
should be true becauseunsigned int
is an unsigned type. MySQL performs the proper conversion between signed and unsigned values in both directions, although a warning occurs if truncation results.bool *error
For output, set this member to point to a
bool
variable to have truncation information for the parameter stored there after a row fetching operation. When truncation reporting is enabled,mysql_stmt_fetch()
returnsMYSQL_DATA_TRUNCATED
and*error
is true in theMYSQL_BIND
structures for parameters in which truncation occurred. Truncation indicates loss of sign or significant digits, or that a string was too long to fit in a column. Truncation reporting is enabled by default, but can be controlled by callingmysql_options()
with theMYSQL_REPORT_DATA_TRUNCATION
option.
This structure is used to send and receive
DATE
,TIME
,DATETIME
, andTIMESTAMP
data directly to and from the server. Set thebuffer
member to point to aMYSQL_TIME
structure, and set thebuffer_type
member of aMYSQL_BIND
structure to one of the temporal types (MYSQL_TYPE_TIME
,MYSQL_TYPE_DATE
,MYSQL_TYPE_DATETIME
,MYSQL_TYPE_TIMESTAMP
).The
MYSQL_TIME
structure contains the members listed in the following table.Member Description unsigned int year
The year unsigned int month
The month of the year unsigned int day
The day of the month unsigned int hour
The hour of the day unsigned int minute
The minute of the hour unsigned int second
The second of the minute bool neg
A boolean flag indicating whether the time is negative unsigned long second_part
The fractional part of the second in microseconds Only those parts of a
MYSQL_TIME
structure that apply to a given type of temporal value are used. Theyear
,month
, andday
elements are used forDATE
,DATETIME
, andTIMESTAMP
values. Thehour
,minute
, andsecond
elements are used forTIME
,DATETIME
, andTIMESTAMP
values. See Section 28.7.24, “C API Prepared Statement Handling of Date and Time Values”.
Traduction non disponible
Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.
Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-c-api-prepared-statement-data-structures.html
L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.
Références
Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.