Update of /cvsroot/modeling/ProjectModeling/Modeling/tests/xmlmodels
In directory sc8-pr-cvs1:/tmp/cvs-serv23691/tests/xmlmodels
Modified Files:
Tag: brch-0_9pre6-1-ModelMasons_base_generation_scheme
README.txt
Log Message:
Updated README
Index: README.txt
===================================================================
RCS file: /cvsroot/modeling/ProjectModeling/Modeling/tests/xmlmodels/README.txt,v
retrieving revision 1.1.1.1
retrieving revision 1.1.1.1.4.1
diff -C2 -d -r1.1.1.1 -r1.1.1.1.4.1
*** README.txt 30 Jul 2002 15:38:55 -0000 1.1.1.1
--- README.txt 26 May 2003 14:42:44 -0000 1.1.1.1.4.1
***************
*** 1,23 ****
The following models are defined:
! 'model_testBothSidesRels.xml' -- used by test_Relationship and
! test_RelationshipManipulation
! 'model_AuthorBook.xml' -- used in test_Attribute, test_Entity,
! test_ImportExport, test_Qualifier, test_SQLExpression and test_SortOrderings
! **Important Note**: please do not use this model as a working example. It is
! here for historical reasons and will be removed as soon as the tests that
! rely on it will be adapted. It has a major flaw in its design: it uses a
! flattened attribute in a very bad way (flattened attributes can only be
! used when inheritance in mapped to a database schema using the 'vertical'
! approach, i.e. a subclass instance gets its data from both the superclass'
! table and its own table which only holds the attributes the subclass adds
! to the superclass' set of attributes).
! 'model_Author_Books.xml' -- used in test_EditingContext
! Note:
- Removed 'used for locking' for attributes 'id' and 'FK_Writer_id' in
- entity 'Writer' so that we can test that the 'usedForLocking' stuff is
- not needed for fetching&saving!
--- 1,47 ----
The following models are defined:
! * 'model_AuthorBooks.xml'
! 'model_StoreEmployees.xml' (.xml/.xml2/.xml3)
! Both models correspond to the one stored, resp., in modules
! testPackages.AuthorBooks and testPackages.StoreEmployees
! They are used by the test-script test_generate_python_code.sh which makes
! sure that every generated packages behave correctly as far as the
! modeling's unittests are concerned (specifically,
! test_EditingContext_Global.py is used for AuthorBooks, and
! test_EditingContext_Global_Inheritance.py for StoreEmployees)
! Note for AuthorBooks:
!
! Removed 'used for locking' for attributes 'id' and 'FK_Writer_id' in
! entity 'Writer' so that we can test that the 'usedForLocking' stuff is
! not needed for fetching&saving!
!
! Note for StoreEmployees:
!
! .xml -- the standard model as stored in testPackages.StoreEmployees
!
! .xml2 -- the same except that entities Executive and SalesClerk share the
! same module 'Employees'
!
! .xml3 -- entities same but entities Executive, SalesClerk and Employee
! share the module 'Employees' (making it impossible to generate
! python code with option -B ie the ''base'' generation scheme)
!
! * 'model_AuthorBook.xml' -- used in test_Attribute, test_Entity,
! test_ImportExport, test_Qualifier, test_SQLExpression and
! test_SortOrderings
!
! **Important Note**: please do not use this model as a working example. It
! is here for historical reasons and will be removed as soon as the tests
! that rely on it will be adapted. It has a major flaw in its design: it
! uses a flattened attribute in a very bad way (flattened attributes can
! only be used when inheritance in mapped to a database schema using the
! 'vertical' approach, i.e. a subclass instance gets its data from both
! the superclass' table and its own table which only holds the attributes
! the subclass adds to the superclass' set of attributes).
!
! * 'model_testBothSidesRels.xml' -- used by test_Relationship and
! test_RelationshipManipulation
|
