Joshua, On 28/11/14 17:01, Joshua Dunham wrote:
Thanks for the tip! It ‘worked’ or at least got me a bit further. Now I have some errors/warnings about the DB and a final error about not being able to represent a timestamp. I don’t think the problem is with the data … but I can’t be sure. I can save the data currently in the DB and start again if there is an issue after the DB upgrade.
In the last week we had in 3.3.0-SNAPSHOT introduced a schema change regarding dates storing for correctly managing timezones. See further details at MARMOTTA-564.
Therefore I suspect you are using the low level loader on a existing database, is that correct? There are two options: start with a new db or update the schema. In case the first solution is not an option because you cannot start from scratch, we can provide you a guide how to upgrade the schema (we'll have to provide it anyway when publishing the new release).
Let us know, please. Cheers, -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 660 2747 925 e: sergio.fernan...@redlink.co w: http://redlink.co
