[Modeling-cvs] ProjectModeling/Modeling/doc/www bug861048.txt,1.2,1.3

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

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

Modified Files:
	bug861048.txt 
Log Message:
doc. updated

Index: bug861048.txt
===================================================================
RCS file: /cvsroot/modeling/ProjectModeling/Modeling/doc/www/bug861048.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** bug861048.txt	20 Dec 2003 15:21:02 -0000	1.2
--- bug861048.txt	20 Dec 2003 15:38:00 -0000	1.3
***************
*** 106,145 ****
  
  See, for example, what happens when we try it with two
! test-models, *AuthorBooks* and *StoreEmployees*::
  
! :*AuthorBooks* is not affected:
!   > cd Modeling
!   > python2.2 ./scripts/bug861048.py tests/testPackages/AuthorBooks/model_AuthorBooks.xml 
!   The model AuthorBooks is not affected by bug #861048
  
!   > python2.2 ./scripts/bug861048.py tests/testPackages/StoreEmployees/pymodel_StoreEmployees.py
!   The model StoreEmployees is affected by bug #861048
!   
!   - PostgreSQL, MySQL, Oracle:
!     connect to your db and correct the schema with the following statements:
!   
!   ---- cut here ----
!   ALTER TABLE ADDRESS DROP CONSTRAINT toEmployee;
!   ---- cut here ----
!   
!   - SQLite; sorry, but SQLite does not support ALTER TABLE, so you have no 
!     other choice but to:
!   
!       1. backup the file containing your database,
!       
!       2. dump your database:
!   	 $ sqlite your_database .dump > dump.db.sqlite
!   
!       3. edit the file dump.db.sqlite and:
!       - in CREATE TABLE ADDRESS (...), remove the statement:
!   CONSTRAINT toEmployee FOREIGN KEY (FK_EMPLOYEE_ID) REFERENCES EMPLOYEE(ID)
!   
!   	(you may have to remove a trailing comma from the previous statement if
!   	 the CONSTRAINT line was the last one before the closing bracket in
!   	 CREATE TABLE)
!   	 
!       4. recreate your database:
!   	 $ mv your_database your_database.backup
!   	 $ sqlite your_database  ".read dump.db.sqlite"
  
  
--- 106,149 ----
  
  See, for example, what happens when we try it with two
! test-models, *AuthorBooks* and *StoreEmployees*:
  
! - *AuthorBooks* is not affected::
  
!     > cd Modeling
!     > python2.2 ./scripts/bug861048.py tests/testPackages/AuthorBooks/model_AuthorBooks.xml 
!     The model AuthorBooks is not affected by bug #861048
! 
! 
! - *StoreEmployees* is affected by the bug::
! 
!     > python2.2 ./scripts/bug861048.py tests/testPackages/StoreEmployees/pymodel_StoreEmployees.py
!     The model StoreEmployees is affected by bug #861048
!     
!     - PostgreSQL, MySQL, Oracle:
!       connect to your db and correct the schema with the following statements:
!     
!     ---- cut here ----
!     ALTER TABLE ADDRESS DROP CONSTRAINT toEmployee;
!     ---- cut here ----
!     
!     - SQLite; sorry, but SQLite does not support ALTER TABLE, so you have no 
!       other choice but to:
!     
!     	1. backup the file containing your database,
!     	
!     	2. dump your database:
!     	   $ sqlite your_database .dump > dump.db.sqlite
!     
!     	3. edit the file dump.db.sqlite and:
!     	- in CREATE TABLE ADDRESS (...), remove the statement:
!     CONSTRAINT toEmployee FOREIGN KEY (FK_EMPLOYEE_ID) REFERENCES EMPLOYEE(ID)
!     
!     	  (you may have to remove a trailing comma from the previous statement
!     	   if the CONSTRAINT line was the last one before the closing bracket
!     	   in CREATE TABLE)
!     	   
!     	4. recreate your database:
!     	   $ mv your_database your_database.backup
!     	   $ sqlite your_database  ".read dump.db.sqlite"