Red Hat Bugzilla – Bug 381771
some database breaks on the hsqldb shipped with fc8 (hsqldb-220.127.116.11-1jpp.4.fc8)
Last modified: 2008-05-08 14:38:02 EDT
Description of problem:
When opening one of my databases, which worked just fine in fc7, oobase
refused to connect to the data source, reporting a error message that a
particular view could not be executed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open oobase, select troublesome database
2. click tableson left pane
3. get error message
Tables and views become available
The view that seems to cause the problem is rather complex, making it hard to
debug. As it is hard to debug by editing repeatedly the zipped xml file that
is oobase's native format, and as the file is critical in my work right now, I
just forced a downgrade to hsqldb-18.104.22.168-2jpp.2, without touching any other
files, and lo and behold, the database works.
Unfortunately, under these circumstances, debugging the view is like searching
a needle in a haystack, so I will for the while have to suffice with the
I use a large UNION SELECT statement and lots of IFNULL and CASE WHEN
If any of the above changed recently, that could be the reason for what
Today, after making a backup, I
modified my database file by removing the offending view, upgraded hsqldb,
and tried to see what the problem was. I resolved the bug, for me, for now,
but have no idea what the issue is.
Essentially, there was a view which was considered offensive by the upgraded
hsqldb. After removing it and upgrading, closing and reopening OOo, I could
at first NOT recreate that view. An error message kept on propping up, which,
because the error box could not be resized, I could not read in its entirety.
However, it was a Java error.
After removing more and more statements, I finally managed to figure out that
there was no specific SQL statement that was offensie. Rather, there was a
particular table (actually, it's a view) that the view editor did not like,
and whenever I would create a view of that view, it would refuse to save the
new, secondary view. Yet, I could save views of other views and tables.
Somehow, after playing with OOo a bit, closing and opening and saving and
rebooting (I was also working on a Wine project and the automounter didn't
seem happy), suddenly I managed to create the view I wanted and save it. Now
everything works fine.
As the issue is now resolved for me, I will suggest to close the bug.