WinSQL - Revision history

Beard at 17:48, 13 March 2020

2020-03-13T17:48:30Z

Beard: /* Easier Query Termination */

2020-03-13T17:47:47Z

‎Easier Query Termination

Beard: /* Better Comment Parsing */

2020-03-13T17:33:01Z

‎Better Comment Parsing

Beard: /* Better Comment Parsing */

2020-03-13T17:32:14Z

‎Better Comment Parsing

Beard: /* Better Comment Parsing */

2020-03-13T17:31:10Z

‎Better Comment Parsing

Beard: /* Clear Recent Files List */

2020-03-13T17:10:48Z

‎Clear Recent Files List

Beard: /* Easier Query Termination */

2020-03-13T15:44:24Z

‎Easier Query Termination

Beard: /* Easier Query Termination */

2020-02-13T15:22:44Z

‎Easier Query Termination

Beard: /* Easier Query Termination */

2020-02-12T23:48:39Z

‎Easier Query Termination

Beard: /* Easier Query Termination */

2020-02-12T23:48:15Z

‎Easier Query Termination

@@ Line 28: / Line 28: @@
 So the default query terminator is "go," which makes sense I guess because that's common syntax in SQL Server, but I'm used to something more streamlined, and even our vendor's software uses queries terminated in the way I've written above, so this configuration change just makes it so much easier to work with thos queries, and it more streamlined.
 = Better Comment Parsing =
@@ Line 69: / Line 59: @@
 Doing this will make sure that any lines that the editor identifies as a comment will not be passed to the server. I, personally, prefer this.

← Older revision		Revision as of 17:47, 13 March 2020
Line 1:		Line 1:

−	= ~~Easier~~ Query Termination =	+	= Better Query Termination =

	I used to use a program called SqlDbx, which is free but it's only 32-bit unless you pay $300 for the paid version. When my workplace moved to Windows 10, I could no longer install the 32-bit Informix ODBC drivers, and so I could no longer use SqlDbx with Informix.		I used to use a program called SqlDbx, which is free but it's only 32-bit unless you pay $300 for the paid version. When my workplace moved to Windows 10, I could no longer install the 32-bit Informix ODBC drivers, and so I could no longer use SqlDbx with Informix.

@@ Line 63: / Line 63: @@
 You have two options:
-# Just use the curly brace commenting when working with Informix and accept that the editor's color highlighting will not identify them as comments, which reduced readability.
+# Just use the curly brace commenting when working with Informix and accept that the editor's color highlighting will not identify them as comments, which reduces readability.
 # Make WinSQL parse comments locally.

@@ Line 57: / Line 57: @@
 <pre>
 Found a non-terminated comment ("/*" with no matching "*/").
-,792 Row(s) affected
+,806 Row(s) affected
 Row(s) affected
 A syntax error has occurred.

← Older revision		Revision as of 17:31, 13 March 2020
Line 41:		Line 41:
	= Better Comment Parsing =		= Better Comment Parsing =

−	The default way WinSQL handles comments is to pass them to the server, which is ~~ridiculous and~~ unnecessary. Anyone using T-SQL or MySQL might not experience issues, but Informix is the oddball that uses <i>curly braces</i> for comments, like <code>{ This is a comment. }</code>	+	The default way WinSQL handles comments is to pass them to the server, which is unnecessary. Anyone using T-SQL or MySQL might not experience issues, but Informix is the oddball that uses <i>curly braces</i> for multi-line comments, like <code>{ This is a comment. }</code>
		+
		+	If you try to use the C-style <code>/* */</code> across multiple lines, like:
		+	<source lang="sql">
		+	/*
		+	select *
		+	from user_rec;
		+	*/
		+
		+	select count(*) as user_count
		+	from user_rec;
		+	</source>
		+
		+	You will get an error, and it will still execute the commented query:
		+	<pre>
		+	Found a non-terminated comment ("/" with no matching "/").
		+	456,792 Row(s) affected
		+	1 Row(s) affected
		+	A syntax error has occurred.
		+	</pre>
		+
		+	You have two options:
		+	# Just use the curly brace commenting when working with Informix and accept that the editor's color highlighting will not identify them as comments, which reduced readability.
		+	# Make WinSQL parse comments locally.
		+
		+	You can make WinSQL parse comments locally by going to: Edit > Options and checking the box "Parse comments locally" in the General tab.
		+
		+	Doing this will make sure that any lines that the editor identifies as a comment will not be passed to the server. I, personally, prefer this.

← Older revision		Revision as of 17:10, 13 March 2020
Line 38:		Line 38:

	Now close and re-open WinSQL.		Now close and re-open WinSQL.
		+
		+	= Better Comment Parsing =
		+
		+	The default way WinSQL handles comments is to pass them to the server, which is ridiculous and unnecessary. Anyone using T-SQL or MySQL might not experience issues, but Informix is the oddball that uses <i>curly braces</i> for comments, like <code>{ This is a comment. }</code>

← Older revision		Revision as of 15:44, 13 March 2020
Line 28:		Line 28:

	So the default query terminator is "go," which makes sense I guess because that's common syntax in SQL Server, but I'm used to something more streamlined, and even our vendor's software uses queries terminated in the way I've written above, so this configuration change just makes it so much easier to work with thos queries, and it more streamlined.		So the default query terminator is "go," which makes sense I guess because that's common syntax in SQL Server, but I'm used to something more streamlined, and even our vendor's software uses queries terminated in the way I've written above, so this configuration change just makes it so much easier to work with thos queries, and it more streamlined.
		+
		+	= Clear Recent Files List =
		+
		+	In WinSQL go to File > "Open Data Folder..."
		+
		+	This opens <code>C:\Users\username\AppData\Roaming\WinSQL</code> in Explorer.
		+
		+	Delete the file <code>RecentFiles.dat</code>.
		+
		+	Now close and re-open WinSQL.

@@ Line 2: / Line 2: @@
 = Easier Query Termination =
-I used to use a program called SqlDbx, which is free but it's only 32-bit unless you pay $300 for the paid version. When my workplace moved to Windows 10, I could no longer install the 32-bit Informix ODBC drivers, and I could no longer use SqlDbx with Informix.
+I used to use a program called SqlDbx, which is free but it's only 32-bit unless you pay $300 for the paid version. When my workplace moved to Windows 10, I could no longer install the 32-bit Informix ODBC drivers, and so I could no longer use SqlDbx with Informix.
 Moving over to WinSQL, I discovered a difference that annoyed me. In SqlDbx, I would write a sequence of queries that create temp tables, like this simplified example:
@@ Line 27: / Line 27: @@
 # Uncheck the checkbox right underneath that which says "Terminators must be on a new line". Now click Ok.
-The apparently want you to write "go" on a new line between every query. Nah! With this configuration change, the above query now runs without issue.
+So the default query terminator is "go," which makes sense I guess because that's common syntax in SQL Server, but I'm used to something more streamlined, and even our vendor's software uses queries terminated in the way I've written above, so this configuration change just makes it so much easier to work with thos queries, and it more streamlined.

@@ Line 24: / Line 24: @@
 I discovered a simple solution:
 # Go to the Edit menu and click Options.
-# Under the General tab, there is a text field in the right pane called "Query terminator string". By default it is set to "go". Change it to ";".
+# Under the General tab, there is a text field in the right pane called "Query terminator string". By default it is set to "go". Change it to ";" (semicolon).
 # Uncheck the checkbox right underneath that which says "Terminators must be on a new line". Now click Ok.
 The apparently want you to write "go" on a new line between every query. Nah! With this configuration change, the above query now runs without issue.

@@ Line 20: / Line 20: @@
 </source>
-In SqlDbx, I could just run this whole thing, it runs the first query and creates the temp table, then the second query could select from the temp table. In WinSQL, it says the table "employees_female" is not in the database. It wasn't treating these as separate queries.
+In SqlDbx, I could just run this whole thing exactly as I've written it. It runs the first query and creates the temp table, then the second query could select from the temp table. In WinSQL, it says the table "employees_female" is not in the database. It wasn't treating these as separate queries.
 I discovered a simple solution: