Author: paul
Date: 2007-02-12 21:26:00 +0100 (Mon, 12 Feb 2007)
New Revision: 4913
Log:
r16153@frost: paul | 2007-02-12 14:25:17 -0600
Add another output variable type code.
Revise an example because Konstantin says it's bad. :-)
Modified:
trunk/refman-4.1/apis-c.xml
trunk/refman-5.0/apis-c.xml
trunk/refman-5.1/apis-c.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:19666
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16147
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13520
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:19666
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16153
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13520
Modified: trunk/refman-4.1/apis-c.xml
===================================================================
--- trunk/refman-4.1/apis-c.xml 2007-02-12 20:20:48 UTC (rev 4912)
+++ trunk/refman-4.1/apis-c.xml 2007-02-12 20:26:00 UTC (rev 4913)
Changed blocks: 2, Lines Added: 12, Lines Deleted: 7; 1725 bytes
@@ -8481,6 +8481,11 @@
<entry><literal>short int</literal></entry>
</row>
<row>
+ <entry><literal>MEDIUMINT</literal></entry>
+ <entry><literal>MYSQL_TYPE_INT24</literal></entry>
+ <entry><literal>int</literal></entry>
+ </row>
+ <row>
<entry><literal>INT</literal></entry>
<entry><literal>MYSQL_TYPE_LONG</literal></entry>
<entry><literal>int</literal></entry>
@@ -8589,13 +8594,13 @@
<listitem>
<para>
- To fetch a SQL <literal>MEDIUMINT</literal> column value, you
- can specify a <literal>buffer_type</literal> value of
- <literal>MYSQL_TYPE_LONG</literal> and use a C variable of
- type <literal>int</literal> as the destination buffer. MySQL
- will convert the <literal>MEDIUMINT</literal> value (a 3-byte
- value) for storage into the <literal>int</literal> (a 4-byte
- variable).
+ If you fetch a SQL <literal>MEDIUMINT</literal> column value,
+ but specify a <literal>buffer_type</literal> value of
+ <literal>MYSQL_TYPE_LONGLONG</literal> and use a C variable of
+ type <literal>long long int</literal> as the destination
+ buffer, MySQL will convert the <literal>MEDIUMINT</literal>
+ value (which requires less than 8 bytes) for storage into the
+ <literal>long long int</literal> (an 8-byte variable).
</para>
</listitem>
Modified: trunk/refman-5.0/apis-c.xml
===================================================================
--- trunk/refman-5.0/apis-c.xml 2007-02-12 20:20:48 UTC (rev 4912)
+++ trunk/refman-5.0/apis-c.xml 2007-02-12 20:26:00 UTC (rev 4913)
Changed blocks: 2, Lines Added: 12, Lines Deleted: 7; 1725 bytes
@@ -8602,6 +8602,11 @@
<entry><literal>short int</literal></entry>
</row>
<row>
+ <entry><literal>MEDIUMINT</literal></entry>
+ <entry><literal>MYSQL_TYPE_INT24</literal></entry>
+ <entry><literal>int</literal></entry>
+ </row>
+ <row>
<entry><literal>INT</literal></entry>
<entry><literal>MYSQL_TYPE_LONG</literal></entry>
<entry><literal>int</literal></entry>
@@ -8715,13 +8720,13 @@
<listitem>
<para>
- To fetch a SQL <literal>MEDIUMINT</literal> column value, you
- can specify a <literal>buffer_type</literal> value of
- <literal>MYSQL_TYPE_LONG</literal> and use a C variable of
- type <literal>int</literal> as the destination buffer. MySQL
- will convert the <literal>MEDIUMINT</literal> value (a 3-byte
- value) for storage into the <literal>int</literal> (a 4-byte
- variable).
+ If you fetch a SQL <literal>MEDIUMINT</literal> column value,
+ but specify a <literal>buffer_type</literal> value of
+ <literal>MYSQL_TYPE_LONGLONG</literal> and use a C variable of
+ type <literal>long long int</literal> as the destination
+ buffer, MySQL will convert the <literal>MEDIUMINT</literal>
+ value (which requires less than 8 bytes) for storage into the
+ <literal>long long int</literal> (an 8-byte variable).
</para>
</listitem>
Modified: trunk/refman-5.1/apis-c.xml
===================================================================
--- trunk/refman-5.1/apis-c.xml 2007-02-12 20:20:48 UTC (rev 4912)
+++ trunk/refman-5.1/apis-c.xml 2007-02-12 20:26:00 UTC (rev 4913)
Changed blocks: 2, Lines Added: 12, Lines Deleted: 7; 1725 bytes
@@ -8720,6 +8720,11 @@
<entry><literal>short int</literal></entry>
</row>
<row>
+ <entry><literal>MEDIUMINT</literal></entry>
+ <entry><literal>MYSQL_TYPE_INT24</literal></entry>
+ <entry><literal>int</literal></entry>
+ </row>
+ <row>
<entry><literal>INT</literal></entry>
<entry><literal>MYSQL_TYPE_LONG</literal></entry>
<entry><literal>int</literal></entry>
@@ -8833,13 +8838,13 @@
<listitem>
<para>
- To fetch a SQL <literal>MEDIUMINT</literal> column value, you
- can specify a <literal>buffer_type</literal> value of
- <literal>MYSQL_TYPE_LONG</literal> and use a C variable of
- type <literal>int</literal> as the destination buffer. MySQL
- will convert the <literal>MEDIUMINT</literal> value (a 3-byte
- value) for storage into the <literal>int</literal> (a 4-byte
- variable).
+ If you fetch a SQL <literal>MEDIUMINT</literal> column value,
+ but specify a <literal>buffer_type</literal> value of
+ <literal>MYSQL_TYPE_LONGLONG</literal> and use a C variable of
+ type <literal>long long int</literal> as the destination
+ buffer, MySQL will convert the <literal>MEDIUMINT</literal>
+ value (which requires less than 8 bytes) for storage into the
+ <literal>long long int</literal> (an 8-byte variable).
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4913 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 12 Feb |