Re: [Hsqldb-user] Recovery problem regarding sequence permissions

[Carl G. <ca...@ca...>]

Hi, I have put together a test application that reproduces this bug. It 
does
exactly what my example below says. There is a readme.txt included in the
attached zip file that has all instructions for compiling and reproducing
the bug.

NOTE - sourceforge won't let me send a "*.zip" file, so this file's 
extension is
".azipfile"


Thanks,

Carl



Fred Toussi wrote:

> This doesn't look possible. When the log is reread, all operations are 
> performed with full admin rights.
>  
> If you want to take this further, please put together a simple test 
> case and submit the database package.
>  
> Fred
>
>     ----- Original Message -----
>     *From:* Carl Gould <mailto:ca...@ca...>
>     *To:* hsq...@li...
>     <mailto:hsq...@li...>
>     *Sent:* 12 May 2005 01:54
>     *Subject:* [Hsqldb-user] Recovery problem regarding sequence
>     permissions
>
>     Hello all,
>
>         I posted this problem to the sourceforge forum, but got no
>     responses, so here goes..
>
>         I am having a problem with database recovery in version 1.7.3, 
> and
>     with the use of system out tracing, I think I may have discovered
>     a bug, but hopefully not.
>
>         The problem seems to be that sequences can only be ALTERed by an
>     ADMIN user. So, if I have a non-admin user issues the folowing SQL:
>
>         SELECT ..., NEXT VALUE FOR MY_SEQ FROM ...
>
>     (lets say that the NEXT VALUE was a 42)
>
>         and
>         INSERT INTO ... (ID, ...) VALUES (42, ...)
>
>         Now suppose that the process is killed unexpectedly. In the .log
>     file this gets translated to:
>
>     ALTER SEQUENCE MY_SEQ RESTART WITH 43
>
>     INSERT INTO ... (ID, ...) VALUES (42, ...)
>
>         So, when I start the DB back up, I get an:
>
>     "Access is denied in statement [ALTER]",
>
>     and database recovery fails.
>
>     I cannot seem to grant permissions on SEQUENCEs.
>
>         Any ideas? The obvious workaround is to compromise my user
>     security, of course, but this is rather messy.
>
>         Thanks,
>
>     Carl G
>