Update of /cvsroot/modeling/ProjectModeling/Modeling/doc
In directory sc8-pr-cvs1:/tmp/cvs-serv20819
Modified Files:
UserGuide.tex abstract.tex
Log Message:
minor review; FAQ in Appendix; start PyModels doc; deleted 4.8
Index: UserGuide.tex
===================================================================
RCS file: /cvsroot/modeling/ProjectModeling/Modeling/doc/UserGuide.tex,v
retrieving revision 1.19
retrieving revision 1.20
diff -C2 -d -r1.19 -r1.20
*** UserGuide.tex 6 May 2003 13:52:01 -0000 1.19
--- UserGuide.tex 19 May 2003 16:05:16 -0000 1.20
***************
*** 49,52 ****
--- 49,53 ----
\appendix
\input{UserGuide/EnvironmentVariables}
+ \input{UserGuide/FAQ}
%
% The ugly "%begin{latexonly}" pseudo-environments are really just to
Index: abstract.tex
===================================================================
RCS file: /cvsroot/modeling/ProjectModeling/Modeling/doc/abstract.tex,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** abstract.tex 20 Feb 2003 21:38:59 -0000 1.3
--- abstract.tex 19 May 2003 16:05:16 -0000 1.4
***************
*** 2,7 ****
relational databases. It relies on a model, based on Entity-Relationship
Modelling, that describes how the two worlds map to each other. From your design
! of such a model, the database's schema and the python code templates for your classes
! are automatically generated, ready to be used. Thus,
once you have designed how your classes should be stored in the RDBMS, you can
focus on the real challenges -- the logic of your business objects -- while
--- 2,7 ----
relational databases. It relies on a model, based on Entity-Relationship
Modelling, that describes how the two worlds map to each other. From your design
! of such a model, the database's schema and corresponding python classes
! are automatically generated. Thus,
once you have designed how your classes should be stored in the RDBMS, you can
focus on the real challenges -- the logic of your business objects -- while
|
