[Modeling-cvs] ProjectModeling/Modeling/doc/UserGuide DefiningaModel.tex,1.15,1.16

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

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

Modified Files:
	DefiningaModel.tex 
Log Message:
Added doc.&links for supported external SQL datatypes

Index: DefiningaModel.tex
===================================================================
RCS file: /cvsroot/modeling/ProjectModeling/Modeling/doc/UserGuide/DefiningaModel.tex,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -d -r1.15 -r1.16
*** DefiningaModel.tex	23 Aug 2003 16:52:36 -0000	1.15
--- DefiningaModel.tex	24 Aug 2003 14:26:18 -0000	1.16
***************
*** 358,362 ****
  
  \item[\code{type}:] this is the associated python type, which can be either
!         \code{string}, \code{'int'}\footnote{Note that python types \code{int}
          and \code{long int} are treated the same way. This is due to different
          DB-adaptors having different behaviours --some can also have a
--- 358,362 ----
  
  \item[\code{type}:] this is the associated python type, which can be either
!         \code{string}, \code{int}\footnote{Note that python types \code{int}
          and \code{long int} are treated the same way. This is due to different
          DB-adaptors having different behaviours --some can also have a
***************
*** 365,377 ****
          (e.g. 42); anyway it sounds reasonable to consider \code{int} and
          \code{long int} as equivalent within the framework's core.}
!         \code{'float'} or \code{'DateTime'} (mapping to egenix's
          \module{mxDateTime} --or to \class{DCOracle2.Timestamp}). You should
          keep
  % [sbigaret] NOTE: this might be checked and/or enforced at some time
  %       \module{mxDateTime}). While this is not (yet) checked, you should keep
!         the externalType and the python type in sync (python \code{string}:
!         SQL \code{CHAR}, \code{VARCHAR} or \code{TEXT}\footnote{if you
!         db-server supports \code{TEXT}}, \code{int}: SQL \code{INTEGER},
!         etc.)
  
  \item[\code{isClassProperty}:] indicates whether the Attribute correspond to a
--- 365,377 ----
          (e.g. 42); anyway it sounds reasonable to consider \code{int} and
          \code{long int} as equivalent within the framework's core.}
!         \code{float} or \code{DateTime} (mapping to egenix's
          \module{mxDateTime} --or to \class{DCOracle2.Timestamp}). You should
          keep
  % [sbigaret] NOTE: this might be checked and/or enforced at some time
  %       \module{mxDateTime}). While this is not (yet) checked, you should keep
!         the \code{externalType} (described below) and the python type in sync
!         (python \code{string}: SQL \code{CHAR}, \code{VARCHAR} or
!         \code{TEXT}\footnote{if you db-server supports \code{TEXT}},
!         \code{int}: SQL \code{INTEGER}, etc.).
  
  \item[\code{isClassProperty}:] indicates whether the Attribute correspond to a
***************
*** 389,397 ****
  
  \item[\code{externalType}:] the SQL type to which this attribute should be
!         mapped. Supported SQL types are: \code{INTEGER}/\code{INT},
!         \code{CHAR}/\code{VARCHAR} (requires a \code{width}, see below),
!         \code{TEXT},
!         \code{NUMERIC} (requires \code{precision} and \code{scale}, see
!         below), \code{TIMESTAMP} and \code{DATETIME}.
  
  \item[\code{precision}, \code{scale}, \code{width}:]
--- 389,406 ----
  
  \item[\code{externalType}:] the SQL type to which this attribute should be
!         mapped. The supported SQL datatypes depend on the adaptor, please
!         refer to their documentation for details:
! 	
! 	\begin{itemize}
! 
!         \item{\bf MySQL:} \ulink{MySQLAdaptorLayer}{http://modeling.sourceforge.net/API/Modeling-API/public/Modeling.DatabaseAdaptors.MySQLAdaptorLayer-module.html}
! 
!         \item{\bf Oracle:} \ulink{OracleAdaptorLayer}{http://modeling.sourceforge.net/API/Modeling-API/public/Modeling.DatabaseAdaptors.OracleAdaptorLayer-module.html}
! 
!         \item{\bf PostgresqlSQL:} \ulink{PostgresqlAdaptorLayer}{http://modeling.sourceforge.net/API/Modeling-API/public/Modeling.DatabaseAdaptors.PostgresqlAdaptorLayer-module.html}
! 
!         \item{\bf SQLite:} \ulink{SQLiteAdaptorLayer}{http://modeling.sourceforge.net/API/Modeling-API/public/Modeling.DatabaseAdaptors.SQLiteAdaptorLayer-module.html}
! 
! 	\end{itemize}
  
  \item[\code{precision}, \code{scale}, \code{width}:]