Yes the source code can be checked out from svn by anyone and changes can be
made to anyplace.
Whether the change will be accepted as part of h2 is another matter. But if it
increases performance without breaking functionality then it is very likely
that it will be accepted in one form or
Hello
We're using h2 db embbeded on our server application. The client
appliaction is available via share (read only!). Our Problem on client
side is the creation of the temp.db file(s) which happens when a
retrieved blob is above 65Kb. So h2 creates temp file on client's
execution directory
Hello folks,
I need to grant all to all my tables. It does not appear that H2
supports the GRANT ALL ON * TO foo functionality. Is there an
equivalent so that I do not have to create a grant statement for each
table?
Thanks for any help,
Baron
--
You received this message because you are
Hi, I have had this exception come up when trying to query a table
This is the table definition
CREATE TABLE `AL_PAC_TBL`
(
`PAC_ID`BIGINT(20) UNSIGNED,
`PAC_STR` VARCHAR(100) PRIMARY KEY,
`EXPIRE_TIME` TIMESTAMP,
`USED_FLAG`
Rami,
Thanks!
I needed a pat on the back...:P
I was wondering if anyone knows about any changes that can be madeor
have been done.would be interested to know
-Ashish
On Wed, Oct 6, 2010 at 5:22 AM, rami.oja...@gmail.com rami.oja...@gmail.com
wrote:
Yes the source code can be
Hi,
the BACKUP statement does not lock the database objects when using the
multi-threaded mode,
and therefore does not block other users. The resulting backup is
transactionally consistent.
How is this possible?
The documentation is incorrect no longer correct. The BACKUP statement
is
I'm no expert, but I took a quick look at the code and can see a method in
FileSystemDisk called createTempFile that looks like it *could* be where
the change is needed. There's a line that reads:
if (inTempDir) {
dir = null;
... I suspect you want it to be dir =
Hi,
Is this a new change? I have an app using multi-threaded mode and the
backup does not block other queries. Does it mean if the backup is
synchronised on the database and the queries are synchronised on the
session then the backup does not block queries?
Or was it found dangerous that
