HyperSQL Database Engine (HSQLDB) Icon

User Ratings

★★★★★
★★★★
★★★
★★
71
0
0
0
4
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
Write a Review

User Reviews

  • longtimer
    1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    This database is very problematic for debugging as error reporting is very poor. This puts the onus on the user to dig into the code to find out where an exception is coming from instead of actually using the error text. One example is a simple right hand truncation error where text is too long for the column width. This results in the error message "data exception: string data, right truncation" in which neither the column nor the text value causing the problem is highlighted. Thus, a programmer has to look at all the text columns and text values to check which is causing the problem. That is a major waste of time and constitutes an obnoxious approach to programming. There are plenty of other examples like this so if you can avoid this DB do so until the authors decide that error reporting is important.

    Posted 05/06/2013
  • hairnnailcom
    1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    This HSQLDB rather good one, but it's too complicated for user with low and average exp!

    Posted 02/12/2013
  • jamesvinyl
    1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    Good analog SQL database

    Posted 02/12/2013
  • hamilyon
    1 of 5 2 of 5 3 of 5 4 of 5 5 of 5

    Never had more headache then with this database. It's compliance with standards is below my own limit of understanding. Writing portable sql with it is exercise in vanity. I have to stick with it, it gets work done, but at what cost? Never a beautiful expressive sql that i write with other db's. Only basic stuff.

    Posted 12/07/2012