Re: Locking rows in case of an INSERT conflict?

Ugh. Sorry for this double post. Google Groups was misbehaving (it told me the first post had been deleted). Gili On 30/11/2012 5:11 PM, Gili wrote: Hi, Is it possible to INSERT into a table and, if a conflict occurs, lock the conflicting table? See also http://stackoverflow.com/que

Inserting data and locking rows in case of a conflict

Hi, I posted a question at http://stackoverflow.com/questions/13614965/select-for-update-and-conflicting-inserts asking whether it is possible to insert into a table and lock the conflicting row in case of a conflict. Is this possible in H2, or in any other database for that matter? Thanks,

Locking rows in case of an INSERT conflict?

Hi, Is it possible to INSERT into a table and, if a conflict occurs, lock the conflicting table? See also http://stackoverflow.com/questions/13614965/select-for-update-and-conflicting-inserts Thanks, Gili -- You received this message because you are subscribed to the Google Groups "H2 Datab

Maven central publication

Hi there, Thanks for this new version. Will it be published on maven central this time ? Regards, Laurent R Le vendredi 30 novembre 2012 07:45:35 UTC+1, Thomas Mueller a écrit : > > *Hello, > > A new version of H2 is available at http://www.h2database.com > (you may have to click 'Refresh'). >

Re: H2 Database Engine: New version 1.3.170 available

Hi there, Thanks for this new version. Will it be published on maven central this time ? Regards, Laurent R -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-

Re: dropping JAQU?

Hi, I think it's worth to revive it once Java 8 is available, using closures for conditions. So instead of: Product p = new Product(); List restock = db.from(p). where(p.unitsInStock).is(0). select(); it would be: List restock = db. select(Person p -> p.unitsInStock == 0); Regards,

dropping JAQU?

Hi Perhaps it's time we dropped our org.h2.jaqu package ? Nobody seems to be being using it, and last time I looked someone was continuing development in a separate repository. Regards, Noel -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To

Re: Can't compile new version 1.3.170 from scratch

Hi, This is quite a common problem, I wonder if there is a way to let Eclipse give a "nice" error message (special source code with a warning or so). Regards, Thomas On Fri, Nov 30, 2012 at 10:37 AM, Manfred Rosenboom wrote: > 1.5 compliant compiling -- You received this message because you a

Re: Can't compile new version 1.3.170 from scratch

Hi Christoph, Many thanks for your hint! I had already used a Java SE 6 SDK, but I had used 1.5 compliant compiling in Eclipse.for the older H2 versions to make them compilable by default.Now everthing works okay :-) Best, Manfred On Friday, November 30, 2012 9:24:25 AM UTC+1, Christoph Läubri

Re: Deadlock after upgrade 1.2.136 to 1.3.169

Hi, It looks like you are using a connection pool, so that physical JDBC connections should be re-used. But in the stack trace, there are a lot of physical JDBC connections created. The only explanations I have is that either the connection pool doesn't work as it should (that's unlikely), your ap

Re: Can't compile new version 1.3.170 from scratch

Make sure you are using an appropiate compiler (1.6 or above) the messages seem to be related to the fact that in 1.5 there is no override annotation allowed for method overriden in interfaces. Am 30.11.2012 09:11, schrieb Manfred Rosenboom: Hi Thomas, I have just downloaded the current versi

Can't compile new version 1.3.170 from scratch

Hi Thomas, I have just downloaded the current version and have tried (as always) to compile the new version in my H2 Eclipse project. Works usually without any problem. But with the new 1.3.170 version I get the following compile errors: DescriptionResourcePathLocationType The