On Fri, 19 Jul 2019 at 21:20, Tim Fielder <tlfiel...@gmail.com> wrote:
> On Friday, July 19, 2019 at 12:47:00 PM UTC-4, Noel Grandin wrote:
>>
>> Use the SCRIPT coomand or tool to dump and restore the db, that is more
>> reliable.
>>
>
> I'm not trying to load a database built in v1.4.197 in .199 - I rebuilt it
> entirely from the raw xml that I'm parsing. Version 1.4.199 literally
> can't find any data in a database it generated from whole cloth less than
> 10 seconds ago.
>
>
>
OK, that's better, so the problem with .199 is not some kind of disk format
issue, the problem is that some query of yours is returning no data.
Unfortunately your stack trace doesn't tell us anything other than that the
result set is empty, so unless you can generate some kind of reduced test
case, I can't really help you much.
The weird stack trace you are seeing in .197 is because you have a varchar
column that you are querying against, but you are passing in a very large
integer value, which tends to hit a rather unfortunate fallback path in our
conversion code (which has been fixed in master).
You would do better to write your query something like
SELECT title, abstract FROM document WHERE docid = '0001179973'
so that the comparison happens on a char basis, instead of having H2 trying
to convert both sides to some integer type.
In fact, that might fix your problem with .199 too
--
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, send an email
to h2-database+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/h2-database/CAFYHVnV4s-HB0cQJQ5_BvVWJrwxEovWb%3Dnjib8QxtzTZ9x12ow%40mail.gmail.com.
