Getting to my point, another handy enhancement would be to have a programmable way of setting the Result method before the script runs.

As an example, suppose XSET was a SqlDbx-specific command.

- - - - -
XSET result = 'G'

SELECT....
- - - - -

This would be a great enhancement for various other SqlDbx options too, like a programmable toggle for "Include Result Text Only" set to Tor F. (XSET textonly = 'T')

In my thinking, anytime XSET (or whatever syntax you decide to use) is placed into a script, sqldbx would understand it and run it, without any errors from databases. Perhaps these commands would need to be at the top and separated somehow. You get the idea.

Jason Lipman

I have a question about exporting result set containing BIGINT columns to excel. They seem to be exported as string, so I either have to CAST those columns to DECIMAL or convert it in excel manually. I tried all three exports available.

An example, when you use DATEDIFF (date1, date2) function in query, the result is a bigint number.

Thanks,
Goran

Right now it returns the row number and the data in that row.

Could you add a new column that shows the object name from which the result came? That would bring tremedous value because sometimes we research a few thousands rows, and want to whittle down to certain objects that contains the value being searched.

Thanks,
Jason Lipman

But I did not found what is that ( I searched in forum and the main site).

Best regards,
Fabricio

1. Provide functionality to view user roles/roles and allow them to be added/removed
2. Provide functionality to allow easy management (add, delete, alter) of indexes for a table.

Cheers. Timo

So far I am enjoying using SqlDbx. I have used a few other free query tools and SqlDbx seems to have a good mix of features and performance. I use for running single Oracle SELECT, UPDATE and DELETE queries.

electronic cigarette
electronic cigarette

OCIServerAttach failed
ORA-12154: TNS:could not resolve the connect identifier specified.

I have three Oracle versions installed. I cannot tell in SqlDbx which version, or which TNSNAMES.ORA file is being referenced. Any ideas?

New and changed features
1. MySQL and Kdb+ support
2. Improved Intellisense
3. Added support for ALTER table statements
4. Scripting to new tab when SHIFT key is pressed
5. ODBC improvements (Indexes, primary / foreign keys)
6. Added ability to use ODBC drivers for some database systems without creating DSN entries
7. SQL Forms
8. Script to new tab when SHIFT key is pressed

Fixes
Long table constraints truncated (Sybase)
1. Incorrect number of affected rows by stored procedure (Sybase)
2. Inconsistent Editor behavior for some shortcut keys
3. Incorrect lower/upper keyword case in some instances
4. sp_procxmode not scripted for stored procedures (Sybase)
5. Search in Results not working for some locales
6. Couple small scripting errors
7. Exception when closing ODBC connections

http://dev.mysql.com/downloads/connector/odbc/

Download ZIP version with no install. Open it and extract file myodbc5.dll to SqlDbx directory.
This will allow you to connect to MySQL by selecting it from "DBMS Type" combo box on the login screen
There's two ways to specify port number if it is different from default (3306).
1. Specify server name as SERVER:PORT
2. Add line PORT=port_number to Options edit box.