Hi,
Am on 175. Have just tried them on 182 and it works. Thanks for your reply!
On Wednesday, November 5, 2014 4:35:58 PM UTC+8, Noel Grandin wrote:
>
> This is working for me.
>
> What version are you using?
>
--
You received this message because you are subscribed to the Google Groups "H2
Hi,
I don't know how it is actually implemented, but conceptually It depends
on your query.
If you do an order by and limit, it'll need to sort it all first before
pulling the first record. So it isn't going to shortcut the query at all.
The limit will improve performance because it only ha
Hi,
I have a large table in which I need to find only one matching record from
the table. If I put in a LIMIT 1, could that improve performance?
If there is a limit, does the engine stop searching once the LIMIT has
been found? Or is the LIMIT applied as a filter after the search has been
Hi,
>From the error codes, you seem to use multiple versions of H2, version
1.3.176 and 1.3.171. I would ensure to use the same version.
> Do you have any idea how we can recover our db file?
The Recover tool create a SQL script. You may have to edit that file
manually I'm afraid.
Regards,
Thom
Hi,
I think part of the exception stack trace is missing (after the last
"caused by"). Could you post it as well?
> Unfortunally I see that now the db is 1.3GB
Did you try using the Recover tool? Could you run it, and post the last 20
lines of the resulting *.sql file please?
Regards,
Thomas
