[Squirrel-sql-commits] sql12/plugins/refactoring/doc readme.html, 1.3, 1.4

[Rob M. <man...@us...>]

Update of /cvsroot/squirrel-sql/sql12/plugins/refactoring/doc
In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv31609/plugins/refactoring/doc

Modified Files:
	readme.html 
Log Message:
Updates to provide better explanations of refactorings.

Index: readme.html
===================================================================
RCS file: /cvsroot/squirrel-sql/sql12/plugins/refactoring/doc/readme.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** readme.html	28 Dec 2006 03:15:01 -0000	1.3
--- readme.html	28 Dec 2006 15:38:51 -0000	1.4
***************
*** 22,26 ****
  
  <center>
! <table cellspacing="5">
  <tr>
  <td align="center">
--- 22,26 ----
  
  <center>
! <table cellspacing="10" cellpadding="5">
  <tr>
  <td align="center">
***************
*** 76,80 ****
  <tr>
  <td align="center">
! Pointbase 4.4
  </td>
  <td align="center">
--- 76,80 ----
  <tr>
  <td align="center">
! Pointbase
  </td>
  <td align="center">
***************
*** 101,107 ****
  
  * Note: If the database doesn't support the refactoring directly with SQL, 
! then the refactoring will be unavailable for that database.  A future release 
! of the refactoring plugin will provide implementations of all refactorings on 
! databases that don't support them directly.
  <p>
  The following table summarizes the refactorings and their availability on 
--- 101,118 ----
  
  * Note: If the database doesn't support the refactoring directly with SQL, 
! then the refactoring will be unavailable for that database.  For example, 
! when this document was written, Apache Derby (10.2.1.6) allowed you 
! to add a new column to an existing table using a SQL statement like :
! <p>
! 'ALTER TABLE ... ADD COLUMN ...'
! <p>
! yet it didn't provide a way to drop an existing column via some SQL statement 
! such as :
! <p>
! 'ALTER TABLE ... DROP COLUMN ...' 
! <p>
! like many other databases do. A future release of the refactoring plugin will 
! provide implementations of all refactorings on databases that don't support 
! them directly.
  <p>
  The following table summarizes the refactorings and their availability on 
***************
*** 352,358 ****
  </table>
  </center>
  <h3>Add Primary Key</h3>
  
! A table which doesn't already have a Primary Key defined can be altered to 
  specify one.  A primary key uniquely identifies each row in the table, and as
  such must consist only of one or more "non-null" columns.  For some databases 
--- 363,374 ----
  </table>
  </center>
+ <p>
+ If you find that a supported database has been updated to support an operation
+ directly via SQL, I would appreciate an email to let me know so that I can 
+ update the refactoring plugin.(manningr [at] users [dot] sourceforge [dot] net)
+ <p>
  <h3>Add Primary Key</h3>
  
! A table that doesn't already have a Primary Key defined can be altered to 
  specify one.  A primary key uniquely identifies each row in the table, and as
  such must consist only of one or more "non-null" columns.  For some databases 
***************
*** 378,382 ****
  <p>
  You will see a dialog displaying all of the columns from the selected table that 
! are available for use in the new primary key.
  <p>
  <center>
--- 394,400 ----
  <p>
  You will see a dialog displaying all of the columns from the selected table that 
! are available for use in the new primary key.  You may also change the name of
! the constraint that is used to enforce the primary key by changing the 
! "Primary Key Name", which by default is set to PK_&lt;Table Name&gt;
  <p>
  <center>
***************
*** 407,411 ****
  at any time and the refactoring will not be applied.
  <p>
- </center>
  <h3>Drop Primary Key</h3>
  
--- 425,428 ----
***************
*** 425,429 ****
  </center>
  <h3>Add Column</h3>
! Columns can be added to an existing table.  
  <p>
  <center>
--- 442,447 ----
  </center>
  <h3>Add Column</h3>
! For most databases, columns can be added to an existing table without dropping 
! the table and re-creating it.
  <p>
  <center>
***************
*** 442,447 ****
  column can be chosen from the type list (the types are standard JDBC types which
  get mapped to vendor-specific types by the dialect specified in the dialect 
! list.  The other fields represent allowable attributes of columns in most 
! databases and should be self-explanatory.
  <p>
  <center>
--- 460,470 ----
  column can be chosen from the type list (the types are standard JDBC types which
  get mapped to vendor-specific types by the dialect specified in the dialect 
! list).  The other fields represent allowable attributes of columns in most 
! databases and should be self-explanatory.  One thing to note regarding types and
! length / precision and scale - precision and scale only apply to number types, 
! such as NUMERIC, DECIMAL, FLOAT, etc.  The length attribute only applies to 
! character and byte types such as VARCHAR, CHAR, BINARY, etc.  In most databases
! when using BLOB and CLOB types, these attributes are ignored since large objects
! have length that is variable and high-capacity (2GB).
  <p>
  <center>
***************
*** 450,453 ****
--- 473,484 ----
  </center>
  <p>
+ The same options that were available for adding primary keys are also available
+ for adding columns (Execute, Show SQL and Edit SQL).
+ <p>
+ <center>
+ <img src="images/add_column/3_add_column_show_sql.jpg"><br>
+ <b><i> Figure 10. The SQL for the new column addition</i></b>
+ </center>
+ <p>
  <h3>Modify Column</h3>
  Existing columns can be modified in most databases, although with many more