Author: wyoung
Date: Tue May 18 04:28:57 2010
New Revision: 2645
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=2645&view=rev
Log:
Expanded sql_*_null documentation in userman
Modified:
trunk/Wishlist
trunk/doc/userman/tutorial.dbx
Modified: trunk/Wishlist
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/Wishlist?rev=2645&r1=2644&r2=2645&view=diff
==============================================================================
--- trunk/Wishlist (original)
+++ trunk/Wishlist Tue May 18 04:28:57 2010
@@ -30,8 +30,6 @@
use the known floor value.
o Check that it works with Connector/C and MySQL 5.1
-
- o Document sql_*_null in userman
o Add to datetime.h: inline DateTime NOW() { return DateTime(); }
Modified: trunk/doc/userman/tutorial.dbx
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/doc/userman/tutorial.dbx?rev=2645&r1=2644&r2=2645&view=diff
==============================================================================
--- trunk/doc/userman/tutorial.dbx (original)
+++ trunk/doc/userman/tutorial.dbx Tue May 18 04:28:57 2010
@@ -354,12 +354,12 @@
Buns” instead. The resulting query would be:</para>
<programlisting>
-SELECT * FROM stock WHERE item = 'Frank’s Brand Hotdog Buns'
</programlisting>
+SELECT * FROM stock WHERE item = 'Frank's Brand Hotdog Buns' </programlisting>
<para>That’s not valid SQL syntax. The correct syntax is:</para>
<programlisting>
-SELECT * FROM stock WHERE item = 'Frank'’s Brand Hotdog Buns'
</programlisting>
+SELECT * FROM stock WHERE item = 'Frank''s Brand Hotdog Buns' </programlisting>
<para>As you might expect, MySQL++ provides that feature, too,
through its <type>escape</type> manipulator. But here, we want both
@@ -488,11 +488,14 @@
<filename>lib/sql_types.h</filename> corresponding to your
SQL schema. These typedefs begin with <type>sql_</type> and
end with a lowercase version of the standard SQL type name,
- with spaces replaced by underscores. For instance, the SQL
- type <type>TINYINT UNSIGNED</type> is represented in MySQL++
- by <classname>mysqlpp::sql_tinyint_unsigned</classname>. (See
- the <link linkend="sql-null">next section</link> for extensions
- to this feature for handling SQL nulls.)</para>
+ with spaces replaced by underscores. There are variants
+ ending in <type>_null</type> that wrap these base types
+ so they’re <link linkend="sql-null">compatible with
+ SQL null</link>. For instance, the SQL type <type>TINYINT
+ UNSIGNED NOT NULL</type> is represented in MySQL++ by
+ <classname>mysqlpp::sql_tinyint_unsigned</classname>. If you drop
+ the <type>NOT NULL</type> part, the corresponding C++ type is
+ <classname>mysqlpp::sql_tinyint_unsigned_null</classname>.</para>
<para>MySQL++ doesn’t force you to use these typedefs. It
tries to be flexible with regard to data conversions,
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits
