#219 Tables not cataloged for SQLBase database

Core (462)
Jim Thomann

Squirrel SQL 1.2b6
Gupta SQLBase JDBC Driver 8.5-13590
SQLBase Server 7.5.1

The Objects tab can not fully populate itself. The
users are available and the folders SYSTEM TABLE,
TABLE, VIEW and UDT are visible within each, but
selecting any of these tables views does not display
any information.

Also, on the UDT folders only, if I click the
'swing-arm' to open the folder the following error is

Error: UDT: java.sql.SQLException: Unsupported method

I have found this database server very case sensitive.
All other clients I have used have similar problems to
varying extents. If I quote both the table and column
names I can execute SELECT statements, however, the
column names are not displayed in the column header of
the results. The column information is available in
the MetaData tab.

I'm sure you noticed that my JDBC and server versions
don't match. Unfortunately, I had no choice and it has
worked, with coersion, as well as I needed it to. If
it would be useful to someone I can retest using the
current version.

I have been able to accomplish what I needed already.
It is perfectly understandable for this to be low priority.

Thank you very much for your work!


  • Rob Manning

    Rob Manning - 2006-01-15

    Logged In: YES

    I tried working with SQuirreL 2.1 final and SQLBase 9.0.1.
    I made some mods to allow some connectivity and capability
    to view data. However, their JDBC driver is woefully
    incomplete. I was able to hack around some things like
    no support for


    However, a show-stopper for editing table data is the
    fact that there is no support for

    Since we retrieve the data via "select * from ...", we
    absolutely require this jdbc api method to work to
    populate the column headers with real labels that we can
    use to build a where clause that fully specifies a row
    for updating.

    Beyond that there may be other api methods that are
    unsupported and are show-stoppers. Unfortunately, Gupta
    chose to just say, 'whatever isn't/won't be implemented
    throws an exception saying "unsupported..."', instead of
    listing the jdbc api methods that it chose not to implement.
    For now, I've given up attempting to get this working as
    it is difficult to see a nominal benefit when so many
    things are busted because of their inadequate JDBC API

    Rob Manning

  • Rob Manning

    Rob Manning - 2006-01-15
    • labels: --> Core
    • milestone: --> 2.1final
    • assigned_to: nobody --> manningr
    • status: open --> closed-wont-fix

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks