Hi,
I have a requirement which would require encryption keys to be maintained
on the server side of our client-server application. When the user logs in
via the client every time, the encryption key is available on the client in
its memory received as a response value to the login call. We wou
That makes sense regarding there being no grantee on the order of the
operations.
As an extension of the question, I am wondering about the clustering
of H2. It seems that non-read only statements are sent to both
databases (and there are clear limitations as outlined in the docs).
While I have n
There is no guarantee. But that is the case with pretty much every SQL
database engine out there.
Note also that there is no global lock. Transactions will acquire
row-level, and perhaps table-level locks, so two or more connections
can actually execute at the same time.
On Mon, Oct 31, 2011 at 1
Hmmm, interesting.
Is there perhaps an error message earlier on in the log?
I ask because I can't see a root cause belonging to H2 anywhere in
that stacktrace.
On Mon, Oct 31, 2011 at 18:42, Elton (GMAIL) wrote:
> Hi Noel,
> Thank you for replying. It is not an issue related to the DB connection
Hi,
Thanks a lot! I found the problem now, it's a limitation of the exclusive
mode. I will try to fix it in the next release.
Regards,
Thomas
On Tuesday, October 11, 2011, Paul Morris wrote:
> a couple of thread dumps attached from the source DB
>
> On 10 October 2011 19:07, Thomas Mueller
>
Hi,
I guess I will be able to implement this in the next release. I will try
using a TreeMap(String.CASE_INSENSITIVE_ORDER). If this is a
problem I might replace it with:
/**
* A hash map with a case-insensitive string key.
*
* *@param* the value type
*/
*public* *class* CaseInsensitive
Hi,
Thanks a lot! I found out using TreeMap(String.
CASE_INSENSITIVE_ORDER) should work. The disadvantage is that it's no
longer a HashMap but a Map, which is a bit slower on Android (interfaces
method calls are a bit slower than class method calls).
Regards,
Thomas
--
You received this message
Noel,
Thanks for the link. But, I did not find anything on the order of the
statements (but perhaps I missed it). Lets say that one connection is
executing and has the lock, and two others are blocked temporarily.
Then after the release, one of the other two will get access and
perhaps lock the
you probably haven't specified the database URL properly.
see http://www.h2database.com/html/tutorial.html#connecting_using_jdbc
steve wrote:
> Hello
> Firstly , thank you for this awesome database. I've upgraded to the
> current release and noticed that the application wasn't functioning as
> ex
Hello
Firstly , thank you for this awesome database. I've upgraded to the
current release and noticed that the application wasn't functioning as
expected. Turns out a database connection could be established by
hibernate.
I've attached a stacktrace.
java.sql.SQLException: Connections could not b
you'd have to provide more information, preferably a test-case.
issue 3 looks like you have multiple machines accessing the same file, and
those machines do not have synchronised clocks.
Sri Sudha wrote:
> Hi,
>
> In our project we are using H2 DB version : h2-1.1.114. We are using
> h2db to sto
see
http://www.h2database.com/html/features.html#multiple_connections
Adam McMahon wrote:
> Hi,
>
> Quick question. As I understand it, H2 handles the synchronization of
> SQL commands. If a number of SQL commands hit the database from a
> variety of connections, do they execute in the order tha
Can anyone please respond to this thread...
--
View this message in context:
http://h2-database.66688.n3.nabble.com/H2-DB-issues-tp3447334p3467197.html
Sent from the H2 Database mailing list archive at Nabble.com.
--
You received this message because you are subscribed to the Google Groups "H2
Hi,
In our project we are using H2 DB version : h2-1.1.114. We are using
h2db to store the active session information, to store the data only
for 2days and the data will be expire after that.
We are facing multiple issues with h2DB.
Issue 1: Sequence not found (Sequence
SYSTEM_SEQUENCE_39
14 matches
Mail list logo