Author: wyoung
Date: Sat Oct 27 08:36:20 2007
New Revision: 1803
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=1803&view=rev
Log:
Small tweaks to userman
Modified:
trunk/doc/userman/userman.dbx
Modified: trunk/doc/userman/userman.dbx
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/doc/userman/userman.dbx?rev=1803&r1=1802&r2=1803&view=diff
==============================================================================
--- trunk/doc/userman/userman.dbx (original)
+++ trunk/doc/userman/userman.dbx Sat Oct 27 08:36:20 2007
@@ -431,11 +431,17 @@
the example table, and prints those values out.</para>
<para>Notice that MySQL++'s <ulink type="classref"
- url="Result"/> objects work similarly to the STL
- <classname>std::vector</classname> container. The only trick
- is that you can't use subscripting notation if the argument
- is ever 0, because of the way we do overloading, so it's
- safer to call <function>at()</function> instead.</para>
+ url="Result"/> and <ulink type="classref"
+ url="Row"/> objects work like an array or the STL
+ <classname>std::vector</classname> container. The only trick is
+ that if you use a variable to subscript one of these objects,
+ it must be of type <type>int</type>, or your C++ compiler
+ isn't likely to know which overload for <methodname>operator
+ []()</methodname> to call. You can avoid this trap by using
+ the <methodname>at()</methodname> instead of using the
+ subscript operator if you don't mind losing the syntactic
+ convenience. It does the same thing, but it isn't overloaded
+ like <methodname>operator []()</methodname>.</para>
<para>The only thing that isn't explicit in the code above is
that we delegate command line argument parsing and connection
@@ -476,9 +482,9 @@
<classname>std::exception</classname> class. Since the library
can indirectly cause exceptions to come from the Standard C++
Library, it's possible to catch all exceptions from MySQL++
- by just catching <classname>std::exception</classname> by
- reference. However, it's better to have individual catch blocks
- for each of the concrete exception types that you expect, and
+ by just catching <classname>std::exception</classname>.
+ However, it's better to have individual catch blocks for
+ each of the concrete exception types that you expect, and
add a handler for either <classname>Exception</classname> or
<classname>std::exception</classname> to act as a "catch-all"
for unexpected exceptions.</para>
@@ -622,6 +628,10 @@
<para>The <type>quote</type> manipulator both quotes strings,
and escapes any characters that are special in SQL.</para>
+
+ <para>MySQL++ provides other manipulators as
+ well. See the reference manual documentation for
+ <filename>manip.h</filename>.</para>
</sect2>
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits
