SQL Power Software Forum

That's great. Thanks for putting it together!

YoungWoo Kim recently pointed out that we weren't exporting Mondrian XML files in Unicode. I've just committed a fix for that problem; if you update to the latest build, now you can use any Unicode character in your Mondrian schema.

-Jonathan

Creating schemas is getting into dangerous territory for Architect--on some systems (Oracle) it's a fairly heavyweight operation (synonymous with creating a new user) and comes with lots of system-specific cruft like default tablespaces, default collation rules, new user passwords, and so on.

I know it's a simple operation in PostgreSQL, but unless we want Architect to take on a whole lot more complexity, I think we should avoid taking on the responsibility of database, catalog, and schema creation.

You could always do it for any particular system in the "USA" tool. But there are nicer DBA tools out there for any given platform (pgAdmin, Navicat, TOAD, Enterprise Manager, etc).

-Jonathan

Someone else brought this to my attention recently too. It appears to be JOptionPane's fault, but only on recent JREs.

I've changed the code in question to use a JDialog instead. Now it's resizable, and it should be the right size by default (please let me know if it isn't).

Sorry for the inconvenience.

-Jonathan

Oops!

I've just checked in the fix for this. The Hudson build should be available shortly. Thanks for pointing out the problem.

-Jonathan

Thanks. I've appended your comments to bug 1490.

I think there are still lots of other deficiencies with logical/physical names. It was never fully implemented, which is why we backed it out of the last release branch.

-Jonathan

Thanks! Filed as bug 2142 (target release 0.9.8).

-Jonathan

Thanks for taking the time to report this problem!

We're about 1 week away from the next public release of Wabit, and I'd like to ensure a fix for this issue is included. Unfortunately, when I open the .rtf file you attached to your initial post, all I see is a blank document.

If you can reproduce this problem and copy all the text from the "details..." text area of the exception report and paste it into a reply here, it will help us diagnose and fix this problem. You should be able to copy the exception message by clicking inside the text area, then pressing Ctrl+A (select all) followed by Ctrl+C (copy).

Thanks again.

-Jonathan

That's great. Thanks for following up on this!

If you can get the sqllite JDBC driver project to accept your patch, please let us know which version it was rolled into, and we'll update our database compatibility list.

Your patch should be an easy sell, because it definitely expands the driver's compatibility with a lot of tools; not just Power*Architect. The DatabaseMetaData calls should not throw an exception just because a particular feature isn't supported by the underlying database. It should return an empty result set which has the proper structure, just as it does after your patch has been applied.

-Jonathan

Not a bad idea for the special case of creating a table via the right-click menu, but I do strongly suggest you give the keyboard shortcuts a chance. They're really fast and easy to learn!

t: new table
r: new identifying relationship
R (shift + r): new non-identifying relationship
ESC: cancel any of the above
c: new column (in selected table)
Enter: show editor panel for currently-selected item(s)
Del or Backspace: delete currently-selected item(s)

-Jonathan

I certainly agree double-clicking a datasource should do the same as clicking it once and pressing start. Double-click is supposed to perform the default action, which would be "add to workspace and create new query" in this case.

-Jonathan

This is filed as bug 2129.

Thanks for bringing this up. This particular problem (and a proposed solution) is already in the bugzilla database as bug 1797.

-Jonathan

Hey Bronius, good to hear from you again.

Since then, castorp has actually contributed a new "run a custom xslt or velocity template" feature to Architect. So you can run off reports using modified XSLTs from right inside the Architect GUI now. No more need for external XSLT tools.

As for the specific changes you're talking about, they sound like a good idea. The team at SQL Power is currently working flat out on Wabit, so I can't take that on at the moment.

Once again, good to hear from you again.

-Jonthan

Followup: current Wabit builds now support dragging in a whole Level in a single operation.

This feature will be part of release 0.9.8.

-Jonathan

Thanks for these suggestions. I've added the penniless number formats just now; the build should be available shortly.

I'm not sure the column size adjustment would always be welcome... how about a "size columns to fit data" action (perhaps on the right click menu) that would just resize all your columns to fit the data? You could do this after changing the font size if you want to fix the column widths.

-Jonathan