[Modeling-cvs] ProjectModeling/Modeling/doc/UserGuide DefiningaModel.tex,1.6,1.7
Status: Abandoned
Brought to you by:
sbigaret
From: <sbi...@us...> - 2003-03-14 14:33:47
|
Update of /cvsroot/modeling/ProjectModeling/Modeling/doc/UserGuide In directory sc8-pr-cvs1:/tmp/cvs-serv26515/doc/UserGuide Modified Files: DefiningaModel.tex Log Message: Fixed ModelValidation.validateEntity_internals(): now iterates on all primary keys, and correctly report an error when a PK is set to be a class property but does not have a default value set to integer zero (this is now enforced since when the default value is None, we get an erroneous error message at EC.saveChanges(): the validation mechanism fails on validating the PK --thanks to Yannick Gingras for reporting the problem) Index: DefiningaModel.tex =================================================================== RCS file: /cvsroot/modeling/ProjectModeling/Modeling/doc/UserGuide/DefiningaModel.tex,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** DefiningaModel.tex 4 Mar 2003 23:15:24 -0000 1.6 --- DefiningaModel.tex 14 Mar 2003 14:33:42 -0000 1.7 *************** *** 920,928 **** compound primary keys), you shouldn't need to expose the PK values as class' attributes. But, ok, if you really want to do that, that is to say, if you ! declare them as class properties, please keep in mind that they should be ! considered {\underline{\bf \sc read-only}} ; if you modifiy them at run-time, ! the framework will not even notice that--it just does not expect it--and ! things will be out-of-control, for sure. You've been warned! ! \end{description} --- 920,933 ---- compound primary keys), you shouldn't need to expose the PK values as class' attributes. But, ok, if you really want to do that, that is to say, if you ! declare them as class properties: ! \begin{itemize} ! \item{} ! you must also define a default value of \code{0} (integer zero) ! \item{} ! please keep in mind that they should be considered {\underline{\bf \sc ! read-only}} ; if you modify them at run-time, the framework will not even ! notice that--it just does not expect it--and things will be out-of-control, ! for sure. You've been warned! ! \end{itemize} \end{description} |