DBX 10.1.6 Released

Nathan Strutz pointed out a bug where DBX would not run from a site running on a port other than 80.  This stemmed from a cross-site scripting fix added in v10.1.3 which did not consider the port.  This has been resolved.

Other changes in this version:
- added print button to server and database panes
- changed button text on secondary nav to allow the current layout to work at 1024x768
- fixed issue where data sample tab would not display all columns if it rendered wider than current window size

I think I'm getting very close to a complete overhaul; the UI is dated and very restrictive by now (and I've been meaning to add support for other rdbms's for years, as well).  The button renaming noted above was due to not having enough space to comfortably display all the options at smaller resolutions, and while I don't think the change creates any problems per se, I can't say I'm totally delighted with having to abbreviate text merely to get it all to fit - definitely a sign that things must be redone.

DBX 10.1.5 Released

I didn't post for the 10.1.4 release, so here are the changes for that:

10.1.4:
- More complete table DDL output
- fixed bugs in table DDL

In the 10.1.5 version, a Data Sample tab was added for tables and views which simply outputs the TOP X rows for the item (I was reviewing some databases created by others and found that I was lacking context for the columns that seeing a few rows of data helped address).

Data sampling can be shut off by setting the dbx.dataSampleRows value to 0 in config.cfm (25 by default).

DBX 10.1.3 Released

Under certain deployment conditions, specifically using hosts file entries and resolving a server which may have multiple IP's/sites configured on it, the relative path references to JS and CSS files can create a cross-site scripting condition which prevents the browser from rendering properly.

v10.1.3 adds some additional code to force fully resolved references to external assets which should mitigate this anomaly.

Note that this isn't really a problem with DBX (or any other application), but rather a weird condition where the multi-homed server is resolving relative references differently than what the client is resolving via its hosts entry.