With 1.4.200 we noticed that the Exclusive Mode handling changed a bit. A 
grep of the Change Log didn't bubble anything up.

The behavior now indicates that Exclusive Mode must always go from 0 to 1,2 
or 1,2 to 0.  

// 1.4.199
SET EXCLUSIVE 0
SET EXCLUSIVE 0 <-- no exception

SET EXCLUSIVE 1
SET EXCLUSIVE 2 <-- no exception

// 1.4.200
SET EXCLUSIVE 0
SET EXCLUSIVE 0 <-- throws exception

SET EXCLUSIVE 1
SET EXCLUSIVE 2 <-- throws exception

Unit test provided here:
https://github.com/mattrpav/h2-validate

Thanks,
Matt Pavlovich

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/1fea69e9-2ebe-4c2d-8cc0-1aaf880b80c0%40googlegroups.com.

Reply via email to