Final Snapshot Jar for 1.9 release

View: New views
4 Messages — Rating Filter:   Alert me  

Final Snapshot Jar for 1.9 release

by Fred Toussi-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Final improvements to version 1.9 are complete and a snapshot jar is
available at:

http://hsqldb.org/support/

This version fixes the bugs that were reported since RC6.

In addition, query optimisation has been enhanced and now covers all
expressions that include OR and can use an index.

Please conduct tests and report not just bugs, but also successful
results.


Fred Toussi

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Hsqldb-user mailing list
Hsqldb-user@...
https://lists.sourceforge.net/lists/listinfo/hsqldb-user

Re: Final Snapshot Jar for 1.9 release

by Thomas Kellerer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Fred Toussi wrote on 03.10.2009 19:47:

> Final improvements to version 1.9 are complete and a snapshot jar is
> available at:
>
> http://hsqldb.org/support/
>
> This version fixes the bugs that were reported since RC6.
>
> In addition, query optimisation has been enhanced and now covers all
> expressions that include OR and can use an index.
>
> Please conduct tests and report not just bugs, but also successful
> results.

I was trying out the new triggers and it seems the BEFORE keyword is not checked correctly.

The following trigger works (copied from the Trigger test)

create trigger person_trg
after insert ON person
referencing new row as newrow
for each row
 insert into log values (newrow.id, 'inserted');

but when I change the AFTER to BEFORE:

create trigger person_trg
before insert ON person
referencing new row as newrow
for each row
 insert into log values (newrow.id, 'inserted');


I get an error: unexpected token: INSERT [SQL State=42581, DB Errorcode=-5581]

The message refers to the INSERT statement in the body (because when I change the trigger definition to use e.g. a DELETE statement, DELETE is the unexcpected token.

When I change the body to use a BEGIN .. END block, the BEFORE keyword works without problems.

Am I missing something or is this indeed a bug?

And it seems the trigger definition is no longer stored in information_schema.triggers (in 1.8 it was stored in the description column). How can I retrieve the trigger source in 1.9?


Regards
Thomas


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Hsqldb-user mailing list
Hsqldb-user@...
https://lists.sourceforge.net/lists/listinfo/hsqldb-user

Re: Final Snapshot Jar for 1.9 release

by Thomas Kellerer :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thomas Kellerer wrote on 03.10.2009 23:57:
> And it seems the trigger definition is no longer stored in
> information_schema.triggers (in 1.8 it was stored in the description
> column). How can I retrieve the trigger source in 1.9?

Forget that, I just didn't look close enougth ;)

Thomas


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Hsqldb-user mailing list
Hsqldb-user@...
https://lists.sourceforge.net/lists/listinfo/hsqldb-user

Re: Final Snapshot Jar for 1.9 release

by Fred Toussi-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thanks.

A BEFORE trigger should not be able to alter the database, while an
AFTER trigger should. A BEFORE trigger can alter the rows to be inserted
or updated. Will check and enforce this for BEGIN ... END blocks.

Fred

On Sat, 03 Oct 2009 23:57 +0200, "Thomas Kellerer" <spam_eater@...>
wrote:

> Fred Toussi wrote on 03.10.2009 19:47:
> > Final improvements to version 1.9 are complete and a snapshot jar is
> > available at:
> >
> > http://hsqldb.org/support/
> >
> > This version fixes the bugs that were reported since RC6.
> >
> > In addition, query optimisation has been enhanced and now covers all
> > expressions that include OR and can use an index.
> >
> > Please conduct tests and report not just bugs, but also successful
> > results.
>
> I was trying out the new triggers and it seems the BEFORE keyword is not
> checked correctly.
>
> The following trigger works (copied from the Trigger test)
>
> create trigger person_trg
> after insert ON person
> referencing new row as newrow
> for each row
>  insert into log values (newrow.id, 'inserted');
>
> but when I change the AFTER to BEFORE:
>
> create trigger person_trg
> before insert ON person
> referencing new row as newrow
> for each row
>  insert into log values (newrow.id, 'inserted');
>
>
> I get an error: unexpected token: INSERT [SQL State=42581, DB
> Errorcode=-5581]
>
> The message refers to the INSERT statement in the body (because when I
> change the trigger definition to use e.g. a DELETE statement, DELETE is
> the unexcpected token.
>
> When I change the body to use a BEGIN .. END block, the BEFORE keyword
> works without problems.
>
> Am I missing something or is this indeed a bug?
>
> And it seems the trigger definition is no longer stored in
> information_schema.triggers (in 1.8 it was stored in the description
> column). How can I retrieve the trigger source in 1.9?
>
>
> Regards
> Thomas
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Hsqldb-user mailing list
> Hsqldb-user@...
> https://lists.sourceforge.net/lists/listinfo/hsqldb-user
--
  Fred Toussi
  fred@...


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Hsqldb-user mailing list
Hsqldb-user@...
https://lists.sourceforge.net/lists/listinfo/hsqldb-user