Updated 02/07/2014-1740: The bug in 3006b which causes an intermittent crash when attempting to logon to a Database Connection, has been fixed along with the following tweaks in Release 3006c:
- New Preferences Option to Hide the External SQL File Load and Save Buttons
- Adding to the Script Library no Longer Clears the Script List
- Double Clicking the Script List now Populates the SQL Text on the Main window
- A little bit of Refactoring
This latest Beta Release of oneSql comes very close to the official Version 1.0 release, which I expect to be within the following two weeks, definitely before the end of July. I have one more language to add (Spanish) and I already have the translations so that should be relatively straightforward.
I also have a few tweaks to the software to do, the Manual to finish and some more testing and then hopefully we will be good to go with a Version 1.0 release. There are a couple of features that make this a fairly major release, so read on 🙂
I’m always keen for more Beta Testers, so if you are interested please CLICK HERE!
One major change in this release is that the stored Password Credentials for the Connections are now stored in an encrypted manner. This stops someone snooping your database password by querying the connection record from the settings database.
There is more to this however. See the image below of the Preferences window from oneSql.
There are two choices for the encryption. The top choice encrypts the Connection Password in such a way that it is then specific to your computer. If you copy oneSql and the Settings Files onto another computer then the Stored Credentials will not work. This choice is ideal for use in a more secure environment, where for example access to databases is only permitted from select computers and / or locations.
The second choice encrypts the Connection Password in such a way that you can copy the oneSql folder from your computer, put it onto your laptop, or another computer, and your stored credentials will work fine.
This also means that you can copy (oneSql does not need an installation, nor does it put any files on your computer outside of the oneSql folder) oneSql onto a USB Drive, run it from that USB Drive on any Mac, Windows or Linux machine you plug it into. Did I mention it will render itself in your native language as well – as long as your native language is either English, Spanish, French, German or Italian ? 🙂
Does copying oneSql to a USB Drive go against the Software License ? No. Restricting access to a single computer either by the installation of Configuration Files or Registry Entries goes against the design remit of Utility software which in my (not so!) humble opinion is the Developers or DBA’s equivalent of a tradesmans tools.
Can you imagine a screwdriver being licensed to only be used on a given object ? What if you had to pay for another license for every object on which you used your screwdriver ? Forget the expense, it’s just not convenient. I don’t want to punish legitimate users of my software in a vain attempt to stop people stealing my software.
My software License for oneSql is simple, and is based on Concurrency. You can use oneSql on one device at once. If you install it on more than one device then you owe me a few extra $$$, which the software is obviously worth or you wouldn’t be bothering to install it multiple times. Site Licenses, Educational Licenses etc. are all available – contact me for further details: firstname.lastname@example.org
Ok, so I diversified slightly(!) in the last paragraph, (in fact, I’ll rewrite the last paragraph and make it its own blog post as I’m sure the licensing question will be asked often.) back to the 3006b release of oneSql.
Please Note that once you have chosen your preferred type of Encryption, you will need to Select Each Connection and Re-input the Password, then Save. This is a one off procedure that is absolutely necessary or else your Stored Credentials will not work.
This release also includes a new Menu – Actions. From the Actions Menu you currently have the following choices available, which are I think self explanatory:
- Execute SQL: Ctrl / Cmd R
- Clear SQL Script
- Clear Results List
- Clear History List
- Clear All
One feature that I put in, took out and have now put back into oneSql is the ability to select a portion of the SQL text and execute just the highlighted selection. I have found this facility very advantageous in similar products and believe it is a worthy addition to the oneSql feature set.
The other fairly major addition in this release is the Script Library. The picture below has been annotated so I’m sure you can see where I’m going with this.
The ability to store SQL Scripts within the SQL database tool, categorised by Connection (or not – if that’s what you prefer) is I believe very important.
Future versions of oneSql will allow far greater capability and flexibility in the Script Library, for now however we have the basics on which to build something extremely useful.
The Script Library window can be accessed from the Tools Menu of oneSql.
IMPORTANT: If you are NOT creating a new oneSql folder from scratch then it will be necesary to update your oneSql Settings file (oneSqlSettings.db in the SupportFiles folder) by opening it with a SQL Tool (oneSql ?!) and executing the following SQL Statement:
CREATE TABLE csh_scr_main (scr_pk INTEGER PRIMARY KEY AUTOINCREMENT, scr_name VARCHAR(50) NOT NULL, scr_script VARCHAR(9999), scr_con_pk INTEGER DEFAULT 0)
This will create the necessary table to store Scripts. This table (and all others required) is automatically created if this is the first time you have used oneSql.
The previous oneSql Beta ran out yesterday (30th June 2014). This release will work during July only, as the commercial release of Version 1.0 will be out before the end of this month.
If you would like to purchase oneSql for the pre-release price of £15 (valid until Version 1.0 arrives) then you can do so from here. You will receive the same upgrades and support as anyone who purchases Version 1.0 later at the more expensive (and as yet undecided) standard price.