The problem is if the same database is opened in a different TIMEZONE, all
the DATE and TIME will be changed!!!
I cannot control if the fields were saved under ONE or another timezone!!
It is up to the database engine to do that...
TIME 00:00 saved under one timezone should be retrieved as
"System property h2.storeLocalTime (default: false). Store the local time.
If disabled, the daylight saving offset is not taken into account."
*I need to know what happens when this property is set to TRUE to a
database managed by 1.3.169 version of H2*
- - It affects DATE and TIME types?
I explained myself wrong...
The DATE and TIME must be presented the same way if the database is
accessed in another timezone! So, original timezone must be taken into
account...
On Sunday, July 23, 2017 at 6:52:58 AM UTC+1, Noel Grandin wrote:
>
> our DATE/TIME fields very specifically do not
I've been using H2 for years (stayed on version h2-1.3.169 because of
inconsistent behavior of the next 1.3.x versions)
Recently i've found a behavior that needed days of debug and is affecting
VERY SENSIBLE information: *the DATE / TIME types behavior across timezones
/ DST*?
I need a
Hi. We recently upgraded from h2-1.3.169 to 176, and we experienced
corruption issues (we have thousands of installed apps)
The solution was to downgrade to 169 (never gave us problems, used for more
than a year).
On Thursday, December 18, 2014 at 7:52:37 AM UTC, Marc Heinz wrote:
Hi
the creation of the TRACE FILE has absolutely nothing to do
with this problem
I agree.
Regards,
Thomas
On Mon, Jan 12, 2015 at 2:07 AM, marcolopes marcolo...@netc.pt wrote:
We are experiencing too many problems with version 1.3.176 (latest stable
1.3 release).
*Is there anything we
We are experiencing too many problems with version 1.3.176 (latest stable
1.3 release).
*Is there anything we should be aware of before downgrading to 1.3.169*?
(we never experienced many problems with this version, used over a YEAR
with thousands of installations of the same software).
--
absolutely
nothing to do with this problem...
On Monday, January 12, 2015 at 1:01:40 AM UTC, marcolopes wrote:
Since we upgrade to *1.3.176* (from 1.3.169) in our final product, dozens
of users are experiencing problems with damaged databases.
Connection STRING used hasn't changed
Since we upgrade to *1.3.176* (from 1.3.169) in our final product, dozens
of users are experiencing problems with damaged databases.
Connection STRING used hasn't changed, and is:
jdbc:h2:file:database;TRACE_LEVEL_FILE=0;TRACE_LEVEL_SYSTEM_OUT=1
Here are a few logs:
It has been like this for countless software versions...
jdbc:h2:file:database;TRACE_LEVEL_FILE=0;TRACE_LEVEL_SYSTEM_OUT=1
On Friday, January 9, 2015 at 7:19:25 AM UTC, Noel Grandin wrote:
what does your DB URL look like?
On 2015-01-09 02:52 AM, marcolopes wrote:
Since we upgrade
Since we upgrade to *1.3.176* (from 1.3.169) in our final product, dozens
of users are experiencing problems with damaged databases. I currently
don't have access to all the logs, but the most recent was this one:
!SESSION 2015-01-08 16:25:53.347 ---
Recovery tool trace:
01-09 01:03:49 jdbc[3]: exception
org.h2.jdbc.JdbcSQLException: Column count does not match; SQL statement:
-- page 24269: data leaf (last) parent: 24276 table: 206 entries: 2
columns: 68
INSERT INTO O_206 VALUES('CFR:2014:181', 'admin', 'EUR:11/04/2012',
'1150-008',
Is there a way to access a complete Change Log?
http://www.h2database.com/html/changelog.html only gives us the latest
releases...
--
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,
Result of the recovery tool on the database that caused the TRACE LOG:
Result:
Column count does not match; SQL statement:
-- page 24269: data leaf (last) parent: 24276 table: 206 entries: 2
columns: 68
INSERT INTO O_206 VALUES('CFR:2014:181', 'admin', 'EUR:11/04/2012',
'1150-008', 'CFR',
1.3.183 ??
On Thursday, December 18, 2014 at 9:07:16 PM UTC, Thomas Mueller wrote:
Hi,
Yes, this looks like the bug that was fixed in version 1.3.183. I'm afraid
this database is not recoverable.
Regards,
Thomas
On Thu, Dec 18, 2014 at 1:53 PM, Dieter Cailliau dieter@gmail.com
not.
Regards,
Thomas
On Fri, Nov 1, 2013 at 7:56 PM, marcolopes marco...@netc.pt javascript:
wrote:
No. Jars are never modified by Eclipse Product Export.
On Friday, November 1, 2013 6:25:51 PM UTC, Noel Grandin wrote:
On Fri, Nov 1, 2013 at 8:16 PM, marcolopes marco...@netc.pt wrote
? Which would also cause
the db to not close when the last connection is closed.
Or maybe you are using a connection pool which may also need to be shut
down.
On Saturday, 2 November 2013, marcolopes wrote:
Thomas, i know what's going on...
1) The first backup is made
2) The database
PM UTC, Thomas Mueller wrote:
Hi,
H2 doesn't miss the unlock. I'm sure this is not a problem in the
database. It is clearly a problem on your side.
Regards,
Thomas
On Sat, Nov 2, 2013 at 4:27 PM, marcolopes marco...@netc.pt javascript:
wrote:
Thomas, this only happens if the user
UPDATE: In my test case, *the unlock is reached, after ~10 seconds*... is
the default DB_CLOSE_DELAY changed to this default? This was confusing me,
as i thought the unlock was never reached, so, it would be a H2 bug.
I assume now that Datanucleus PMF.close is not closing the connection.
db URL? Which would also cause the
db to not close when the last connection is closed.
Or maybe you are using a connection pool which may also need to be shut
down.
On Saturday, 2 November 2013, marcolopes wrote:
Thomas, i know what's going on...
1) The first backup is made
2
will be corrupt. Don't blame us for that.
If you want to backup the database while it is open, use the backup SQL
statement. Otherwise you need to close the database.
Regards,
Thomas
On Sat, Nov 2, 2013 at 2:51 PM, marcolopes marco...@netc.pt javascript:
wrote:
I opted to ZIP it myself using
I don't really understand the behavior of this parameter on the *
Backup.execute* method.
I thought it would disable the possible log info, but, inspecting the
code, it goes beyond that.
The problem with the current approach is: if quiet=false, there is an
attempt to LOCK the database... and
the BACKUP SQL statement, not the Backup standalone tool.
Regards,
Thomas
On Fri, Nov 1, 2013 at 6:39 PM, marcolopes marco...@netc.pt javascript:
wrote:
I don't really understand the behavior of this parameter on the *
Backup.execute* method.
I thought it would disable the possible log info
OSX
What do you mean with exported?
Regards,
Thomas
On Fri, Nov 1, 2013 at 6:34 PM, marcolopes marco...@netc.pt javascript:
wrote:
H2 Driver: h2-1.3.169.jar
IDE: Eclipse 3.7 RCP (OSGI)
Target platforms: Windows, Linux and MAC OSX
We recently implemented automatic backup
No. Jars are never modified by Eclipse Product Export.
On Friday, November 1, 2013 6:25:51 PM UTC, Noel Grandin wrote:
On Fri, Nov 1, 2013 at 8:16 PM, marcolopes marco...@netc.pt javascript:
wrote:
'
We export as an Eclipse Product, so, it creates a NATIVE executable
file,
just like
the properties file, or finding it, but
properties are invalid, or whatever...
On 11/04/2013 12:46 PM, marcolopes wrote:
Hi Thomas,
I'm using H2 1.3.169, and cannot start the server with the -properties
parameter.
The server won't start (it starts ok without any parameters).
*Here
Hi Thomas,
I'm using H2 1.3.169, and cannot start the server with the -properties
parameter.
The server won't start (it starts ok without any parameters).
*Here is the code*:
server=Server.createWebServer(-properties /foldername);
server.start();
*I took a look at H2
My doubt is: are there any structural differences between the 1.2 and 1.3
versions that make the the DATABASE itself incompatible?
On Wednesday, April 18, 2012 4:16:55 PM UTC+1, Thotheolh wrote:
I think you can dump the database into a SQL script using SCRIPT function
and downgrade to 1.2
Is there any known incompatibility downgrading from the last 1.3 version to
the last 1.2?
The databases where created with 1.2.147, upgraded using 1.3.166, and now
are running on 1.2.147 again
Thanks.
--
You received this message because you are subscribed to the Google Groups H2
Database
Hi Thomas,
It's not that easy, because i'm using a persistence layer
(Datanucleus) and not direct h2 access...
As a programmer i know all info is useful, and surely a test case is
the best option.
Knowing that the problem was introduced in version h2-1.3.156 (and
up), don't you have a hint?
Another question: As we have hundreds of clients using H2 database,
many of them are already using H2 1.3
Can we downgrade to 1.2 without any issues, using a database already
managed by version 1.3?
Thanks.
--
You received this message because you are subscribed to the Google Groups H2
UPDATE
- org.h2.message.DbException: The connection was not closed by the
application - was resolved. Does not change anything.
- Tested in Windows 7 64 and Windows XP
- Tested with H2 embedded and server (no extra parameters used in the
connection string)
jdbc:h2:file:/xxx
- Strangely,
UPDATE
- Problem was introduced in H2 version h2-1.3.156!
--
You received this message because you are subscribed to the Google Groups H2
Database group.
To post to this group, send email to h2-database@googlegroups.com.
To unsubscribe from this group, send email to
/org/h2/tools/Server.html#main_String...
If you running inside of eclipse it would be better not to use
external config files.
On 24 ноя, 19:06, marcolopes marcolo...@netc.pt wrote:
Great! Works like a charm.
I have a few doubts:
1) As far as i can see, the embedded server does not take
, marcolopes marcolo...@netc.pt wrote:
Thanks! That solved the problem (at least for now!)
Can you please tell me:
if i set the value on the console, where is the value stored?
And if i set it through the Connection URL, does it get stored the
same way?
How can i consult the actual
I have tested H2 as a server, and now i have it embedded in a
Eclipse RCP Java App.
Everything works just fine connecting to the Database engine. Embedded
(local) connection jdbc:h2:[file:][]
Now, can i connect to the H2 HTTP Console using the Embedded server?
Virtually, all Eclipse RCP views
...@gmail.com wrote:
You should not use console but just start web server directly from
your app
org.h2.tools.Server.createWebServer().start();
for example on plugin initialization and then manually open views or
editors with browser and point it to correct url.
On Nov 24, 6:11 pm, marcolopes
H2 is not SLOW. Is one of the fastest RDBMS i have tested to date!
I need help explaining WHY i need to CONNECT to the database using the
WEB MANAGER (H2 console) to get the fantastic speed of this DB
engine... I accidentally tested my app when CONNECTED through the H2
WEB console et voilá,
Vladykin sergi.vlady...@gmail.com wrote:
Seehttp://h2database.com/html/grammar.html#set_db_close_delay
On 23 ноя, 23:04, marcolopes marcolo...@netc.pt wrote:
Thanks for the reply.
Is there a way of keeping the database opened (or a keep alive
setting) ?
On Nov 23, 7:37 pm, Sergi
39 matches
Mail list logo
