[Modeling-cvs] ProjectModeling/Modeling/doc/UserGuide EnvironmentVariables.tex,1.11,1.12

[<sbi...@us...>]

Update of /cvsroot/modeling/ProjectModeling/Modeling/doc/UserGuide
In directory sc8-pr-cvs1:/tmp/cvs-serv18723/doc/UserGuide

Modified Files:
	EnvironmentVariables.tex 
Log Message:
Updated w/ info for MySQL

Index: EnvironmentVariables.tex
===================================================================
RCS file: /cvsroot/modeling/ProjectModeling/Modeling/doc/UserGuide/EnvironmentVariables.tex,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -d -r1.11 -r1.12
*** EnvironmentVariables.tex	30 Jul 2003 18:11:09 -0000	1.11
--- EnvironmentVariables.tex	21 Jan 2004 14:16:47 -0000	1.12
***************
*** 132,135 ****
    {\code{'7.2'} (default), \code{'7.3'}}
  \hline
! \end{longtableiii}\label{tab:env-vars-core}
  
--- 132,153 ----
    {\code{'7.2'} (default), \code{'7.3'}}
  \hline
! \end{longtableiii}\label{tab:env-vars-postgresql}
! 
! \newpage
! \section{Mysql specific\label{env-vars-mysql}}
  
+ \begin{longtableiii}{p{1cm}p{11cm}|p{3cm}}{code}{Name}{Description}{Possible values} 
+ \lineiii{MDL_MYSQL_SERVER_VERSION}{}{}
+ \lineiii{}
+   {The framework uses MySQL version number to determine whether SQL92
+ \code{JOIN} statements can be used; if not, the corresponding clause is added
+ to the \code{WHERE} clause. This is because MySQL servers up to 4.0 do not
+ handle \code{JOIN} statements in a standard way, making it impossible to
+ generate a valid SQL query when more than 2 joins are involved.
+ ~
+ If the environment variable is left unset, it defaults to the value returned
+ by \code{MySQLdb.get_client_info()}.}
+   {\code{'3.23'}, \code{'4.0'}, \code{4.0.11a-gamma} (see at end of
+   description for the default value)}
+ \hline
+ \end{longtableiii}\label{tab:env-vars-mysql}