Author: wyoung
Date: Tue May 18 19:48:21 2010
New Revision: 2651
URL: http://svn.gna.org/viewcvs/mysqlpp?rev=2651&view=rev
Log:
Replaced discussion of raising the field limit for SSQLS in the SSQLS
chapter with a link to the same info in the configuration chapter.
Modified:
trunk/doc/userman/ssqls.dbx
Modified: trunk/doc/userman/ssqls.dbx
URL:
http://svn.gna.org/viewcvs/mysqlpp/trunk/doc/userman/ssqls.dbx?rev=2651&r1=2650&r2=2651&view=diff
==============================================================================
--- trunk/doc/userman/ssqls.dbx (original)
+++ trunk/doc/userman/ssqls.dbx Tue May 18 19:48:21 2010
@@ -793,23 +793,9 @@
configurables you might want to tweak.</para>
<para>The first configurable value sets the maximum number of
- data members allowed in an SSQLS. It’s 25 out of the box,
- set by the <varname>$max_data_members</varname> variable at the
- top of <filename>ssqls.pl</filename>. Beware, making this value
- larger increases the size of <filename>ssqls.h</filename>
- quadratically<footnote>
- <para>
- If you’re curious:
- <phrase role="math">
- LOC = 18.5x<superscript>2</superscript> + 454.5x + 196.4
- </phrase>
- </para>
- </footnote>; this will increase compile time, and can even
- make the file uncompilable due to compiler limits. Before you
- increase this value, take a good, hard look at your database schema
- and ask if it’s really the best design. Almost always,
- having so many columns is a sign that you need to refactor the
- table.</para>
+ data members allowed in an SSQLS. This is discussed elsewhere,
+ in <xref linkend="max-fields"/>. Beware the warnings there about
+ increasing this value too much.</para>
<para>The second configurable is the default floating point
precision used for comparison. As described above (<xref
_______________________________________________
Mysqlpp-commits mailing list
[email protected]
https://mail.gna.org/listinfo/mysqlpp-commits
