Friday, March 14, 2008

SQLTools++ on Sourceforge.net

I was thinking about offering users the opportunity to provide feedback, submit bugs, ask for help, request new features etc. Therefore I had to decide how to do that. The straightforward solution would have been to add a forum and a bug tracker (e.g. bugzilla) to my already existing SQLTools++ homepage.

But then I thought there are already sites out there that offer these functions and more. So I opted for an Sourceforge.net project... Back to the roots, the original SQLTools is also hosted there, although no longer maintained.

The project request was approved very quickly, so here we are:

http://sourceforge.net/projects/sqlt-pp/

Still the Sourceforge team has not managed yet to upload the existing CVS archive to the sourceforge CVS system but apart from that one already can do a lot of things there:

- Of course download all the available stuff
- Use the "Tracker" feature to submit bugs, request features etc.
- Discuss in forums (Currently "Help" and "Open discussion" are available)

I think this is quite useful and hope the users out there (are there any? :-)) will be able to benefit from it as well.

Best Regards,
Randolf

2 comments:

Anonymous said...

I don't know if this is the good place to report it, but I found a bug in SQLTools(++).

In the object browser (F12) the NVARCHAR2 length are incorrectly reported.
My fields are displayed as NVARCHAR2(400), but if I check the DDL with the "Load" command (or in another tool) I notice that the field is NVARCHAR2(200).

I hope it's a simple fix...

Randolf said...

Please download the "Development Build" either from my homepage (http://www.sqltools-plusplus.org:7676/) or from "http://sourceforge.net/projects/sqlt-pp/" and let me know if it fixes your problem or not. A corresponding bug has already been raised and fixed. See here:

http://sourceforge.net/tracker/index.php?func=detail&aid=1939328&group_id=220648&atid=1050077

The bug tracker at sourceforge.net is also the best place to submit new bugs resp. check if a bug has already been reported.