Hi,
> I also had the same problem with GMT time e.g 'z',
> instead of a offset - it didn't seem limited just to -05:00.
Yes, I also saw that. The problem is now be fixed in the trunk and in the
latest jar file (available in the download page).
Regards,
Thomas
--
You received this message becau
Just a quick follow up: I also had the same problem with GMT time e.g 'z',
instead of a offset - it didn't seem limited just to -05:00.
Thanks for the quick response,
Keith
On Tue, Oct 25, 2011 at 2:15 AM, Thomas Mueller <
thomas.tom.muel...@gmail.com> wrote:
> Hi,
>
> I can reproduce this probl
Hi,
I can reproduce this problem. I guess the only workaround is to _not_ use
timezone offsets (-05:00) at the moment. This bug will be fixed in the next
release.
Regards,
Thomas
On Tuesday, October 25, 2011, Keith Donald wrote:
> Eastern but my server is running in pacific.
>
> On Mon, Oct 24
Eastern but my server is running in pacific.
On Mon, Oct 24, 2011 at 11:33 PM, Thomas Mueller <
thomas.tom.muel...@gmail.com> wrote:
> Hi,
>
> Strange... What timezone do you live in?
>
> Regards,
> Thas
> Am 25.10.2011 05:29 schrieb "Keith" :
>
>> This was noticed when manually inserting a recor
Hi,
Strange... What timezone do you live in?
Regards,
Thas
Am 25.10.2011 05:29 schrieb "Keith" :
> This was noticed when manually inserting a record using the H2
> Database Console. Very puzzled by this, but H2 seems unable to parse
> any of the following timestamps:
>
> 2011-10-26 8:00:00-05:0
This was noticed when manually inserting a record using the H2
Database Console. Very puzzled by this, but H2 seems unable to parse
any of the following timestamps:
2011-10-26 8:00:00-05:00
2011-10-26 7:00:00-05:00
2011-10-26 6:00:00-05:00
2011-10-26 5:00:00-05:00
2011-10-26 4:00:00-05:00
2011-10
