PragmaSQL Version History

---

Version 1.0.0.37

• Demo period is extended to 120 days
• All previous demo licenses were deleted, so that you can request a new demo activation key for extra 120 day evaluation. You can delete licence.lic file from PragmaSQL installation folder and enter the new activation key provided to you by PragmaSQL Online.
  
• Script editor was enhanced to support renderer add-ins. You can now develop custom renderer add-in and users can choose your renderer for rendering query results.
• PragmaSQL Virtual Result Renderers source code published as a sample for custom renderer add-in development. Download Source Code

---

Version 1.0.0.36

---

Version 1.0.0.35

- APP-27: Objects in the Object Group editor are sorted by Type, Name. Type order is a following
 * Table,
 * Stored procedure,
 * User defined functions and
 * Views
- APP-28 : After initializing Object Grouping editor, first parent node is not automatically expanded anymore.
- APP-29 : After changing database in the script editor Fast script preview was showing script for the object in wrong database. This issue was fixed.
- Database object scripting functionality changed.  PragmaSQL Scripter wizard is used for scripting. Most important improvement is that we can save our selected object names, along with the schema name,  for later use, which is a crucial feature especially needed while doing intergration testing.

---

Version 1.0.0.34

* [APP-24] Bug resolved for details see the blog entry
* [APP-25] Search and replace dialog improved.
* [APP-26] Fast script preview fature added. You can preview object scripts of the objects in a script editor by pressing Alt+F2. This functionality is similar with CoolIris addon for Firefox.

---

Version 1.0.0.33

* [APP-21] Change Database added to object search
* [APP-22] "Add Object To Group" and "Show Grouping Statistics" context menu items added to Object Explorer and Script Editor.
* Some bug fixes applied to Object Grouping.
* [COR-10] ReadOnly property added to ITextEditor interface.
* [COR-11] ScriptExecuting and ScriptExecuted events added to IScriptEditor interface. AddIn developers can cancel script execution by hooking to ScriptExecuting event
* [COR-12] Some methods and properties added to ITextEditor interface in order to provide addin developers with runtime ToolStripItem add/remove functionality.
 - In order to be able to add/remove ToolStripItems to notification tool strip AddItemToNotificationStrip, RemoveItemFromNotificationStrip methods  and NotificationStripItemCount property added
 - In order to be able to add/remove ToolStripItems to addin tool strip AddItemToAddInStrip, RemoveItemFromAddInStrip methods  and AddInStripItemCount property added
* [COR-14] EditorClosing and EditorClosed events added to ITextEditor interface. AddIn developers can cancel closing of a text editor programatically by hooking to
EditorClosing event. Also EditorClosing,EditorClosed and EditorReady events were added to IEditorServices interface for similar purposes. EditorReady is fired after
a text/script editor is ready with its content.
* [COR-15] OpenProject(string fileName) method added to IProjectExplorerServices interface.
 

---

Version 1.0.0.32

- Incremental search added (APP-7)
- Bit columns can be sorted (APP-14)
- Default configuration is loaded when Execute In Multiple Databases dialog is opened(APP-17)
- Application version number added to splash screen (APP-18)
- Database connection is opened in a background worker thread allowing the user to cancel connection that take too much to open (APP-19)
- Turkish locale problem of the highlighter resolved (APP-20)
- EditorServices.CurrentEditor.SaveToFile() removes file dirty indicator (COR-8)
- ExternalTools Add-In configuration moved to Tools->Options->Modules ( EXTLS - 1)

---

Version 1.0.0.31

- Proxy problem while product activation partly resolved. Static proxy settings for IE are used for proxy authentication.

---

Version 1.0.0.30

-  Packing error related with the new machine key generation method resolved
- ToolStripTextBox bug resolved in Change History Viewer

---

Version 1.0.0.29

- APP - 8: Script Table As Script functionality added to Object Explorer
- APP - 9: Triggers(All) node added to object explorer
- APP-10: Convert only selection to upper/lower case else convert all functionality added
- APP-11: Text copy  functionality added to messages window in script editor
- APP-12: Folded code block problem in search/replace resolved.
-Machine key generation for demo installations was changed but old version is still supported.

---

Version 1.0.0.28

- Execute In Multiple databases support added to Script Editor. You can execute same script against multiple servers/databases. New button added near existing Execute, Stop, Check Syntax,Show Plan buttons.  When you click Execute In Multiple Databases button you are prompted to select database connections and once you press OK your script is executed in the selected databases.You can store selected databases as default and sure restore the list from default.

- IConfigSvc added to PragmaSQL.Core.dll You can publish your configuration UserControls implementing IConfigContentEditor in Tools->Options dialog under Modules node.

- Update check performed on application startup moved to a background worker thread. If there is a new version of PragmaSQL you are notified with a messagebox.

- Saved Connections dialog modified. Connections are listed by server/user and default database and grouped by server

- Object Explorer modified. You can connect to the same server with different username and these connections are listed in Object Explorer as seperate root nodes. In previous version only one connection per server was allowed.

- Script Editor modified. Connections to the same server with differen users are listed in the Server combobox. In previous version only one item per server was listed.

---

Version 1.0.0.27

- ExternalTools add-in  developed and added to the distribution
- New functionality added to PragmaSQL.Core library such as HostServices.EvalMacro.
- Check for new versions added. PragmaSQL checks for updates on start if Options->General -> Check for updates on start is selected. Also you can check for updates manually using main menu Help->Check For Updates.

---

Version 1.0.0.26

- While logging object change history, CreatedBy username was taken from PragmaSQL System connection. This was corrected so that CreatedBy username will be taken from the current connection.

- DB Object Search created false search script when AND/OR specified.

- Script result tab captionsconvention was changed. Result page caption will use the pattern Query {BatchNo}.{Result No}[{Record Count}]
- Options menu moved under Tools menu

---

Version 1.0.0.25

- Due to character problems with Turkish during result export to excel, encoding option was added to PragmaSQL.
Previous versions used default encoding both in text editor and during excel export.
You can change encoding from View->Options->Script Editor->Text Editor->Other page.

---

Version 1.0.0.24

- Workspace restore feature added. PragmaSQL saves script/text editor and
opened project when application closed and restores workspace when opened.

- ITextEditor interface defines method void Select( CaretPosition startPos, CaretPosition endPos )
However we need an overload for this method which accepts offset value for selection start/end and looks like this
void Select(int startOffset, int endOffset)

- Access to screen cursor on the editors via the core dll.

- I can access the current ScriptEditor via HostServicesSingleton.HostServices.EditorServices.CurrentScriptEditor
and the current TextEditor via HostServicesSingleton.HostServices.EditorServices.CurrentTextEditor
but I want to be able to access the current editor that the user is editing regardless of knowing whether it is a script
or a text editor. Is it possible to have a ITextEditor valued CurrentEditor property in EditorServices?

- We can change casing(upper/lower case) all script in the current editor or all keywords.

- I can filter db objects, search any object in database.. Also i need filter columns in a specific table...
For example i write [TableName]. then code completion list displays columns in [TableName].
When i begin to write anything in the filter box, contents changes to all db objects..
Is it possible to upper/lower case only selected script?

- Execution stops when there is error in the script.

- When Allow Caret Beyon EOL causes error in search

- Roles Object privileges show filters do not work

- HostServicesSingleton.HostServices.EditorServices.CurrentScriptEditor.WordAtCursor considers minus sign a word terminator. What I expected it would do is that it should grab the whole string between the nearest whitespaces (space, tab, CRLF, etc. ) surrounding the current caret position.

---

Version 1.0.0.23

- Object change history accessable through script editor
-  DB search accessable through script editor
- Some performance improvements
- Some core functionality reorganization.

---

Version 1.0.0.22

Code completion proposal caching

---

Version 1.0.0.21

Connection management issues resolved.

Single instance script editor management added.

---

Version 1.0.0.20

• (Resolved) Main Menu -> File -> Save Script As asks twice for the file name.
• (Resolved) Script editor does not evaluate selected server and database correctly when values changed by the user. This bug causes script editor to open new script editors (ie. when trying to modify a stored procedure or open and inspect table data) with wrong connection specification.

---

Version 1.0.0.19

• SQL Server 2000 related bug in Object Grouping fixed
• Other SQL Server 2000 related compatibility issues fixed.
o System table sys.objects renamed to sysobjects
o System table sys_foreign_keys renamed to sysforeignkeys
o object_id column named to id column in sysobjects table.
• Object Grouping bug fixed. (When user rejects saving changes change flag was not cleared.)
• Shared Scripts bug fixed. (When user rejects saving changes change flag was not cleared.)
• Shared Snippets bug fixed. (When user rejects saving changes change flag was not cleared.)
• Script editor bug fixed. When rendering query results in same tab if the scrip executed does not return any result set unhandled exception was thrown.
• SQL Management Add-In critical bug related to Modify Table fixed. Primary key columns of the table were not identified correctly. This bug caused wrong table modification scripts to be generated.

---

Version 1.0.0.18

• New add-in for server and database management deployed (SQLManagement Add-In)
• Script editor now renders query results in two optional ways
1. Each result set is put in own tab
2. All result sets are put in the same tab and rendered horizontally
You can change default rendering behavior by navigating to View->Options->Script Editor->Text Editor->Other option panel
• Code completion bug resolved: When script does not contain any of the local variables, local tables or table aliases script editor throws unhandled exception when code completion is invoked.
• Local variable, table and table alias analysis is now optional to improve code completion start up performance. You can turn this setting by navigating to View->Options->Script Editor->Text Editor->Other options panel.
• Text Editor font can be changed by navigating to View->Options->Script Editor->Text Editor->General option panel.


IMPORTANT: You have to install version 1.0.0.18 of PragmaSQL application in order to use SQLManagement addin. It is also strongly recommended that you update HtmlHelp2 addin you have previously installed.

---

Version 1.0.0.17

• You can now delete objects from Object Explorer by using the context menu.
• Microsoft HTML Help2 integration add-in deployed.

HtmlHelp2 AddIn Installation:

1. Copy PragmaSQL.AddIn.HtmlHelp2.zip to your local
2. Start PragmaSQL’ and open AddIn Manager Dialog by navigating to Tools->AddIn Manager Menu.
3. Click Install AddIn button in AddIn Manager Dialog. Select the add-in zip previously copied in the open file dialog.
4. Restart PragmaSQL
5. You will get Contents, Index, Search, Index Results and Configure Help menu items under Help menu.
6. Click Configure Help menu item. Choose Help Collection you want to use from the list (For example: SDK documentation for SQL Server 2005) and click Apply button.
7. You can use Help2 Options dialog to change other behaviors of the addin.

---

Version 1.0.0.16

Application hang caused by regular expressions identified and solved by moving regular expression evaluation to background thread with default timeout of 1 second.

---

Version 1.0.0.15

• Object names can now be used as search criteria for Database Search
• Uninstall PragmaSQL added as start menu shortcut.
• Search and Replace behavior of the script editor modified.
• Web Search added to main menu. You can now use Google, Yahoo and other search engines for fast search from PragmaSQL web browser.
• AddIn framework integrated to PragmaSQL. New addins utilizing Object Explorer, Project Explorer, Shared Scripts, Shared Snippets, Text Editor, Script Editor and extending PragmaSQL can easily be plugged to the main application. You only need to reference PragmaSQL.Core.dll in you .NET project. PragmaSQL.Core includes core services to communicate with the main application and many other helper utilities.

---

Version 1.0.0.5

1) Modified script indicator auto remove

When scriptable objects (stored procedures, functions, views and triggers) are applied to database, depending on your choice, “*” is removed from the caption of the script editor. You can change this behavior by navigating to Main Menu -> View -> Options panel and change “Auto remove modified indicator…” option. If this option is not checked “*” will be preserved in the script editors caption until script is saved (default behavior)

2) Defining Code Block

You can now define code blocks marked by special single line in-comment tags. PragmaSQL Code Blocks are analogous to Visual Studio regions. Following single line in-comment tags are used to identify the code blocks.

#block: Marks the beginning of the code block
 #endblock: Marks the end of the code block

In order to activate code blocks you have to navigate to View -> Options -> Script Editor -> Text Editor ->General option panel and check “Show folding marker” and “Fold code blocks” options. Then you will be able to fold your code between --#block and --#endblock tags.

SHORTCUT: In the Script editor select the code snippet you want to make a folding code block. Right click the selected text and in the opening context menu click “Mark selection as code block” and give description for the code block.

IMPORTANT NOTE: If “Show fold markers” is not checked code blocks will not be showed as folding regions in the script editor although “Fold code blocks” and “Show fold markers for highlighted code blocks” options are checked.

3) Context menu item “Modify (Append to current) “added to Object Explorer

We define stored procedures, functions, views and triggers as scriptable objects. We can modify these objects by double clicking or selecting Modify context menu item from Object Explorer. This method opens new script editor for each object we want to modify (Default behavior). Another alternative (newly added) is opening these objects by clicking “Modify (Append to current)” context menu item. This way all objects are opened in the same editor as separate code blocks