Hi David -- Thanks for your input. I checked the drivers in both James releases and they're identical: Derby 10.14.2.0. So I don't anticipate any versioning issues. And this page on the Apache Derby site suggests you're right even if the driver was upgraded: https://db.apache.org/derby/docs/10.14/devguide/tdevupgradedb.html. Without changing the database URL, it looks like Derby would consider this a "Soft upgrade" (that's nice that Derby allows for smooth transitions to newer versions).
Another potential issue is that the James developers may have updated the database structure since 3.3.0, but I don't see any indication of that in the change logs. I'll be attempting this migration soon. Thanks again for your feedback! Rich P From: "David Matthews" <m...@dmatthews.org.INVALID> To: "James Users List" <server-user@james.apache.org> Date: 04/18/2024 08:56 AM Subject: Re: Migrating database -- James 3.3.0 to 3.8.1 >Hello -- > >I'd like to upgrade a James instance (Spring wiring) from 3.3.0 to 3.8.1. >The 3.3.0 instance uses the standard embedded Derby database. To migrate >the data, can I simply copy the existing Derby database to the new 3.8.1 >directory? If not, what is the procedure for upgrading? I think so; I'm basing this on experience with Derby and another application (ie James not involved). But I believe my experience is backed up by the Derby mission statement, claiming that the database directory can be simply coy/pasted as required. That is my experience anyway. -- David Matthews m...@dmatthews.org --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
