[Squirrel-sql-commits] sql12/doc quick_start.html,1.30,1.31
A Java SQL client for any JDBC compliant database
Brought to you by:
colbell,
gerdwagner
Menu
▾
▴
[Squirrel-sql-commits] sql12/doc quick_start.html,1.30,1.31
|
From: Rob M. <man...@us...> - 2007-04-07 12:00:18
|
Update of /cvsroot/squirrel-sql/sql12/doc In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv19088/doc Modified Files: quick_start.html Log Message: various fixes. Index: quick_start.html =================================================================== RCS file: /cvsroot/squirrel-sql/sql12/doc/quick_start.html,v retrieving revision 1.30 retrieving revision 1.31 diff -C2 -d -r1.30 -r1.31 *** quick_start.html 4 Apr 2007 10:35:48 -0000 1.30 --- quick_start.html 7 Apr 2007 11:59:55 -0000 1.31 *************** *** 295,300 **** class path. <P ALIGN="CENTER"><IMG SRC="images/chg_driver_2.png" BORDER="0" ! ALT="Change ! Driver dialog (Extra Class Path tab)"></A></P> <P>The <EM>Add</EM> button will display a File Open dialog allowing --- 295,299 ---- class path. <P ALIGN="CENTER"><IMG SRC="images/chg_driver_2.png" BORDER="0" ! ALT="Change Driver dialog (Extra Class Path tab)"></P> <P>The <EM>Add</EM> button will display a File Open dialog allowing *************** *** 457,466 **** <P>Every SQL statement that is successfully executed is also added to the ! drop-down history list, which is shown below. <P ALIGN="CENTER"><IMG SRC="images/sql_history_list.png" BORDER="0" ALT=""Torn off" query results"></P> ! This list can then be used to find and re-execute previously executed statements. The drop-down list allows you to pick the SQL statement, and clicking the --- 456,465 ---- <P>Every SQL statement that is successfully executed is also added to the ! drop-down history list, which is shown below.</P> <P ALIGN="CENTER"><IMG SRC="images/sql_history_list.png" BORDER="0" ALT=""Torn off" query results"></P> ! <P>This list can then be used to find and re-execute previously executed statements. The drop-down list allows you to pick the SQL statement, and clicking the *************** *** 470,474 **** using the SQL History dialog which is accessed by the icon ( <img src="images/history_dialog_icon.png" align="middle"> ) which is next to the blue ! arrow. The SQL History window is shown below. <P ALIGN="CENTER"><IMG SRC="images/sql_history_dialog.png" BORDER="0" --- 469,473 ---- using the SQL History dialog which is accessed by the icon ( <img src="images/history_dialog_icon.png" align="middle"> ) which is next to the blue ! arrow. The SQL History window is shown below.</P> <P ALIGN="CENTER"><IMG SRC="images/sql_history_dialog.png" BORDER="0" *************** *** 484,497 **** limitations of data editing, including the use of the Popup window to import and export data. In addition, there are two things that you need ! to know about editing in the SQL Results: <DL> <LI>To enable editing in the SQL Results tables, you must set the ! "SQL Results" entry in the Session Properties to "Editable Table". <LI>Editing is only allowed when the SQL that was executed ! consists of: <PRE> "SELECT <column list> FROM <single_table_name>" or "SELECT <column list> FROM <single_table_name> WHERE ..." ! </PRE> In addition, the name of the table must be unique within the entire DB. This means that if you have multiple catalogs or schemas which have that same table name defined in them, Squirrel cannot determine which --- 483,498 ---- limitations of data editing, including the use of the Popup window to import and export data. In addition, there are two things that you need ! to know about editing in the SQL Results:</P> <DL> <LI>To enable editing in the SQL Results tables, you must set the ! "SQL Results" entry in the Session Properties to "Editable Table".</LI> <LI>Editing is only allowed when the SQL that was executed ! consists of: ! <PRE> "SELECT <column list> FROM <single_table_name>" or "SELECT <column list> FROM <single_table_name> WHERE ..." ! </PRE> ! In addition, the name of the table must be unique within the entire DB. This means that if you have multiple catalogs or schemas which have that same table name defined in them, Squirrel cannot determine which *************** *** 499,503 **** is just a bit stupid on this point: it will let you edit the data, and then tell you that it cannot update the DB when you exit the cell being ! changed.) </DL> <P><A NAME="ContentsTab"> --- 500,504 ---- is just a bit stupid on this point: it will let you edit the data, and then tell you that it cannot update the DB when you exit the cell being ! changed.)</LI> </DL> <P><A NAME="ContentsTab"> *************** *** 862,870 **** them. The command will typically need the name of the file to edit. This may be done by using "%f" where you want the name of the file to ! go in that command, so, for example, instead of typing: <PRE> ! xterm -e vi myfilename ! </PRE> you could type <PRE> ! xterm -e vi %f ! </PRE> which makes the command more general and avoids the need for you to edit the command for each file. <LI>Click on "Execute". This causes the cell data to be exported --- 863,875 ---- them. The command will typically need the name of the file to edit. This may be done by using "%f" where you want the name of the file to ! go in that command, so, for example, instead of typing: ! <PRE> ! xterm -e vi myfilename ! </PRE> ! you could type ! <PRE> ! xterm -e vi %f ! </PRE> ! which makes the command more general and avoids the need for you to edit the command for each file. <LI>Click on "Execute". This causes the cell data to be exported *************** *** 880,885 **** For example, to run VI on Linux you may need to enter the command: <PRE> ! xterm -e vi %f ! </PRE> to have VI run in a window visible to you. If you just enter "vi %f" as the command, you will not get a window to operate in. Other commands (e.g. gimp) provide their own windows, so the extra step will not be --- 885,891 ---- For example, to run VI on Linux you may need to enter the command: <PRE> ! xterm -e vi %f ! </PRE> ! to have VI run in a window visible to you. If you just enter "vi %f" as the command, you will not get a window to operate in. Other commands (e.g. gimp) provide their own windows, so the extra step will not be *************** *** 894,897 **** --- 900,904 ---- column, you can enter the "File:" and "Command:" field information and click on "Apply". + <h3><a name="Limitations"></a>Limitations</h3> *************** *** 1164,1175 **** when all tabs will not fit within a single run.</P> ! <p align="center"> <table> <tr> ! <td width="40%" align="right"><img src="images/stacked_tabs.png" ! border="0"></td> <td width="10%"></td> ! <td width="40%" align="left"><img ! src="images/scrollable_tabs.png" border="0"></td> </tr> <tr> --- 1171,1185 ---- when all tabs will not fit within a single run.</P> ! <P> ! <center> <table> <tr> ! <td width="40%" align="right"> ! <img src="images/stacked_tabs.png" border="0"> ! </td> <td width="10%"></td> ! <td width="40%" align="left"> ! <img src="images/scrollable_tabs.png" border="0"> ! </td> </tr> <tr> *************** *** 1179,1183 **** </tr> </table> ! </p> <P><B>Show Main Window Tool Bar</B> - If checked then the tool bar --- 1189,1194 ---- </tr> </table> ! </center> ! <P><B>Show Main Window Tool Bar</B> - If checked then the tool bar *************** *** 1208,1215 **** name is too long for the label then the full name will be displayed in a tooltip.</P> ! For more information see ! <A HREF="#logs">Logs</A> ! . ! </P> <P><B>Configuration File</B> - This (display only) setting tells you --- 1219,1223 ---- name is too long for the label then the full name will be displayed in a tooltip.</P> ! For more information see <A HREF="#logs">Logs</A>. <P><B>Configuration File</B> - This (display only) setting tells you *************** *** 1217,1224 **** If the file name is too long for the label then the full name will be displayed in a tooltip.</P> ! For more information see ! <A HREF="#logs">Logs</A> ! . ! </P> <H4>SQL Tab</H4> --- 1225,1231 ---- If the file name is too long for the label then the full name will be displayed in a tooltip.</P> ! ! For more information see <A HREF="#logs">Logs</A>. ! <P> <H4>SQL Tab</H4> *************** *** 1233,1237 **** <P><B>Large Scrip Statement Count</B> - By default, a script is ! considered large if it has > 200 SQL statements selected for execution in the script. When this is set to zero, large script execution support is disabled. Large script support consists of the following behavior --- 1240,1244 ---- <P><B>Large Scrip Statement Count</B> - By default, a script is ! considered large if it has more than 200 SQL statements selected for execution in the script. When this is set to zero, large script execution support is disabled. Large script support consists of the following behavior *************** *** 1241,1245 **** of the session window at the end of running many statements summarizing the details of execution (timing, statement type and count, etc).</li> ! <li>The message "SQL Statement x of y <some sql...>" is still displayed in the results panel to indicate progress.</li> <li>The history bar isn't updated during large script execution.</li> --- 1248,1252 ---- of the session window at the end of running many statements summarizing the details of execution (timing, statement type and count, etc).</li> ! <li>The message "SQL Statement x of y <some sql...>" is still displayed in the results panel to indicate progress.</li> <li>The history bar isn't updated during large script execution.</li> *************** *** 1248,1252 **** many statements in large scripts (especially those with statement counts in the thousands). ! </P> <H4>SQL Tab (Debug)</H4> --- 1255,1259 ---- many statements in large scripts (especially those with statement counts in the thousands). ! <P> <H4>SQL Tab (Debug)</H4> *************** *** 1375,1379 **** Note that this option does not affect display in the Popup window, where newlines actually become new lines. ! </P> <H4>CHAR, VARCHAR, LONGVARCHAR (SQL Types 1, 12, -1)</H4> --- 1382,1386 ---- Note that this option does not affect display in the Popup window, where newlines actually become new lines. ! <P> <H4>CHAR, VARCHAR, LONGVARCHAR (SQL Types 1, 12, -1)</H4> *************** *** 1390,1394 **** Note that this option does not affect display in the Popup window, where newlines actually become new lines. ! </P> <P><B>Allow LONGVARCHAR type to be used in WHERE clause</B> - When --- 1397,1401 ---- Note that this option does not affect display in the Popup window, where newlines actually become new lines. ! <P> <P><B>Allow LONGVARCHAR type to be used in WHERE clause</B> - When *************** *** 1884,1898 **** move them to the other box You must leave at least one column in the "use columns" box, and the column in the "use columns" box must be ! sufficient to uniquely identify each ro in the table, e.g. the primary key fields for the table The "Reset" button restores the column name ! lists to the way they were whe you opened the window <BR Remember to ! click "OK" when you are done <BR> If you define a set of columns to use in the WHERE clause and then edit ! som other column, SQuirreL will warn you that "1 duplicate row" is ! about to b created. Since you have told SQuirreL to not look at the edited column it does no recognize that the new data is different than ! the old data so i gives you a warning. In this case there is no problem ! and you should jus tell SQuirreL to go ahead with the update. </DL> --- 1891,1905 ---- move them to the other box You must leave at least one column in the "use columns" box, and the column in the "use columns" box must be ! sufficient to uniquely identify each row in the table, e.g. the primary key fields for the table The "Reset" button restores the column name ! lists to the way they were when you opened the window <BR> ! Remember to click "OK" when you are done <BR> If you define a set of columns to use in the WHERE clause and then edit ! some other column, SQuirreL will warn you that "1 duplicate row" is ! about to be created. Since you have told SQuirreL to not look at the edited column it does no recognize that the new data is different than ! the old data so it gives you a warning. In this case there is no problem ! and you should just tell SQuirreL to go ahead with the update. </DL> |