<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-2666093586628945183</id><updated>2011-11-27T19:38:05.960-05:00</updated><title type='text'>SqlDbx Development</title><subtitle type='html'>Everything about SqlDbx Database IDE.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://sqldbx.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://sqldbx.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>SqlDbx</name><uri>http://www.blogger.com/profile/13464081178324594567</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>6</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-2666093586628945183.post-1476777411223714037</id><published>2008-11-23T21:57:00.003-05:00</published><updated>2008-11-23T22:30:05.800-05:00</updated><title type='text'>SqlDbx current state  and planned new features</title><content type='html'>Currently working on version 3.27. It's almost done. Couple of things left to test and make sure nothing got broken. Big change in this release will be change to Editor. We are adding variable pitch font support. It's not that I personally like but we actually need to do it in order to support &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_0"&gt;Asian&lt;/span&gt; and &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_1"&gt;Chinese&lt;/span&gt; fonts. Even &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_2"&gt;mono space&lt;/span&gt; &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_3"&gt;Asian&lt;/span&gt; fonts have at least two different widths. Originally Editor was not designed to support variable fonts but it was &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_4"&gt;surprisingly&lt;/span&gt; easy to add it. The only complicated thing is column selection mode. Another new feature is &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;SQL&lt;/span&gt; &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;formatter&lt;/span&gt;. Initial version has some quirks but pretty functional.&lt;br /&gt;One request we getting a lot is to make possible to run &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;SqlDbx&lt;/span&gt;  from &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;USB&lt;/span&gt; key without installing database client software on user computer. I think it is possible to do. The idea is to have all &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;SqlDbx&lt;/span&gt; configuration stored in file instead of registry and then copy database client files to flash  and then on &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;startup&lt;/span&gt; set environment variables, create private registry entries in order to make database client think that it is installed.&lt;br /&gt;Also will be adding ability to filter objects on a left pane. Looked at couple other products and how they do it. Did not find one I &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_11"&gt;particularly&lt;/span&gt; like. I am thinking about doing it very in a different way.&lt;br /&gt;Basically I want to make it look like &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_12"&gt;SQL&lt;/span&gt; select statement. For example to show all tables whose name starts with "AB" and table named "&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_13"&gt;MYTABLE&lt;/span&gt;" plus procedures with names like "*_production_*" you will enter something like this:&lt;br /&gt;(TYPE == 'TABLE' and (NAME like 'AB*' or NAME == '&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_14"&gt;MYTABLE&lt;/span&gt;') or (TYPE == 'PROCEDURE' and NAME like '*_production_*')&lt;br /&gt;&lt;br /&gt;TYPE and NAME are predefined column names. Some other columns are OWNER, DATE_CREATED.&lt;br /&gt;One more suggestion from our users is to add ability to easy select child records when if you select parent record in Result Grid. Idea here is to figure out if current result set in Result grid contains primary key and then find out what table(s) reference it and then give menu item to allow to select rows from child table.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2666093586628945183-1476777411223714037?l=sqldbx.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://sqldbx.blogspot.com/feeds/1476777411223714037/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=2666093586628945183&amp;postID=1476777411223714037' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/1476777411223714037'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/1476777411223714037'/><link rel='alternate' type='text/html' href='http://sqldbx.blogspot.com/2008/11/sqldbx-current-state-and-planned-new.html' title='SqlDbx current state  and planned new features'/><author><name>SqlDbx</name><uri>http://www.blogger.com/profile/13464081178324594567</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-2666093586628945183.post-3961230883004541984</id><published>2008-06-19T23:28:00.002-04:00</published><updated>2008-06-19T23:44:13.411-04:00</updated><title type='text'>Features for next version</title><content type='html'>Version 3.23 is &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_0"&gt;realized&lt;/span&gt; and all known issues seem to be fixed. Now we will take some time and work on improving existing features. One of the main feature which will be looked at is &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;Intellisense&lt;/span&gt;. Currently it's fast and useful but limited in certain situations. One of the issue is Intellisense implemented as one peace of code which handles &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;it&lt;/span&gt; for all different databases and it became pretty messy. &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;Sybase&lt;/span&gt; and Microsoft &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;SQL&lt;/span&gt; Server are very different from Oracle and DB2 so the plan is to separate code for different servers which should make it simplier and easier to extend.&lt;br /&gt;One of the distinctive features of SqlDbx is how fast it compare to other tools. There's always ways to improve it.  Will try couple of things in this area. Also it's time to improve help file.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2666093586628945183-3961230883004541984?l=sqldbx.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://sqldbx.blogspot.com/feeds/3961230883004541984/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=2666093586628945183&amp;postID=3961230883004541984' title='13 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/3961230883004541984'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/3961230883004541984'/><link rel='alternate' type='text/html' href='http://sqldbx.blogspot.com/2008/06/features-for-next-version.html' title='Features for next version'/><author><name>SqlDbx</name><uri>http://www.blogger.com/profile/13464081178324594567</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>13</thr:total></entry><entry><id>tag:blogger.com,1999:blog-2666093586628945183.post-1001401516590931532</id><published>2008-04-30T22:34:00.003-04:00</published><updated>2008-04-30T22:47:04.526-04:00</updated><title type='text'>Things to do next</title><content type='html'>&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;Ok&lt;/span&gt;, release 3.20 is out and now is the time to think what to do next. There's a lot of interest in feature which puts results of every query into a new result tab. I personally think it's not such a great idea. It's easy to end up with a lot of tabs and then it's too confusing. What I am thinking about doing is to add query results to a new tab when Shift key is pressed at the time of query execution. Will implement it this way and see how it works. The other thing I want to improve &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;Intellisense&lt;/span&gt;. &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;SQL&lt;/span&gt; is not easy language to build &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;Intellisense&lt;/span&gt; for. It's not very structured but there's always ways to improve. Another feature which I probably will put into one of the next releases is option to put connection into a read only mode. Basically it will detect any INSERT/UPDATE/DELETE statements and will not execute them.&lt;br /&gt;Couple days ago decided to do some performance testing between &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;SqlDbx&lt;/span&gt; and some other &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;similiar&lt;/span&gt; products. Was pleasantly surprised that &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;SqlDbx&lt;/span&gt; is faster then any of them and sometimes by large margin and I still thing there's room for improvement.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2666093586628945183-1001401516590931532?l=sqldbx.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://sqldbx.blogspot.com/feeds/1001401516590931532/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=2666093586628945183&amp;postID=1001401516590931532' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/1001401516590931532'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/1001401516590931532'/><link rel='alternate' type='text/html' href='http://sqldbx.blogspot.com/2008/04/thing-to-do-next.html' title='Things to do next'/><author><name>SqlDbx</name><uri>http://www.blogger.com/profile/13464081178324594567</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-2666093586628945183.post-8625011105825769860</id><published>2008-03-24T22:53:00.004-04:00</published><updated>2008-03-30T01:41:48.435-04:00</updated><title type='text'>Upcoming release of SqlDbx 3.19</title><content type='html'>Major feature of this upcoming release is the Unicode support.  There will be two versions of &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;SqlDbx&lt;/span&gt; available: &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;Ansi&lt;/span&gt; and Unicode. Two versions will be basically the same with some minor differences.&lt;br /&gt;We decided to have two different versions because it seems easier to maintain and update the code and not everybody needs Unicode to begin with. Unicode version handles everything in Unicode. Some peaces of &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;SqlDbx&lt;/span&gt; were pretty easy to convert to Unicode and some were not. Editor, &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;UI&lt;/span&gt; controls and Results Grid required some minor changes. Most problems were related to the way different Database Servers implement Unicode support in different versions. &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;Sql&lt;/span&gt; Server and DB2 were the easiest to convert. They have &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;API&lt;/span&gt; &lt;span class="blsp-spelling-corrected" id="SPELLING_ERROR_6"&gt;similar&lt;/span&gt; to &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;ODBC&lt;/span&gt; which is Unicode "aware". The most&lt;br /&gt;time consuming was &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;Sybase&lt;/span&gt; support. Documentation is sparse and not very clear in some areas.&lt;br /&gt;Seems that everything is working pretty well now.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2666093586628945183-8625011105825769860?l=sqldbx.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://sqldbx.blogspot.com/feeds/8625011105825769860/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=2666093586628945183&amp;postID=8625011105825769860' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/8625011105825769860'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/8625011105825769860'/><link rel='alternate' type='text/html' href='http://sqldbx.blogspot.com/2008/03/upcoming-release-of-sqldbx-319.html' title='Upcoming release of SqlDbx 3.19'/><author><name>SqlDbx</name><uri>http://www.blogger.com/profile/13464081178324594567</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-2666093586628945183.post-9149470432308437444</id><published>2008-02-03T01:46:00.000-05:00</published><updated>2008-02-08T23:00:30.206-05:00</updated><title type='text'>SqlDbx Version 3.16 is out</title><content type='html'>Adding column (block) mode support to Script Editor was not as simple as I anticipated, but it's done and I think it stacks up pretty good against other editors which support block mode.&lt;br /&gt;Last couple of weeks talked to some of our users and it's interesting how some of the features and options they ask for are already implemented, but they never found out about them. One of these features is an ability to save and restore workspace state between restarts. This can be turned on in Options on General Tab, just check "Enable Session State". Also you can save / load it at any time. Look under File-&gt;Save Session State and File-&gt;Load Session State. Another example is scripting of objects from Object View pane. By default object definition goes to active Script window. This can be changed in Options-&gt;Scripting.&lt;br /&gt;Next release will be mostly small fixes and performance improvements in some areas like generating thousands of inserts, export to Excel.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2666093586628945183-9149470432308437444?l=sqldbx.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://sqldbx.blogspot.com/feeds/9149470432308437444/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=2666093586628945183&amp;postID=9149470432308437444' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/9149470432308437444'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/9149470432308437444'/><link rel='alternate' type='text/html' href='http://sqldbx.blogspot.com/2008/02/sqldbx-version-316-is-out.html' title='SqlDbx Version 3.16 is out'/><author><name>SqlDbx</name><uri>http://www.blogger.com/profile/13464081178324594567</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-2666093586628945183.post-6782077965019151425</id><published>2008-01-13T16:31:00.000-05:00</published><updated>2008-01-19T19:32:15.695-05:00</updated><title type='text'>Version 3.15 released</title><content type='html'>What I realized recently after talking to some of our customers that they do not know about some of the useful features we have implemented. So I decided to start describing some of them.&lt;br /&gt;One of the feature which is pretty useful is ability to generate SELECT, INSERT, DELETE, UPDATE SQL statements directly from Results Grid. This functionality is available if you right click in Results Grid and select "Generate" menu item. You also can select multiple areas in Result Grid by holding Ctrl key.&lt;br /&gt;Recently released version 3.15 has two new nice features. Both of them are on Script Editor pop up menu. In Script Editor click on database object name then right click and select menu item "Script Object to new Window". Object definition should open in new window, or you can select "Sync Object View" and  if object found  in Object view it will be made visible.&lt;br /&gt;Now I started working on version 3.16. Main changes in 3.16 will be around Script Editor. Editor will support column selection / copy /paste mode.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/2666093586628945183-6782077965019151425?l=sqldbx.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://sqldbx.blogspot.com/feeds/6782077965019151425/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=2666093586628945183&amp;postID=6782077965019151425' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/6782077965019151425'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/2666093586628945183/posts/default/6782077965019151425'/><link rel='alternate' type='text/html' href='http://sqldbx.blogspot.com/2008/01/version-315-released.html' title='Version 3.15 released'/><author><name>SqlDbx</name><uri>http://www.blogger.com/profile/13464081178324594567</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
