On Fri, Aug 3, 2012 at 3:22 AM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
> Since you used hibernate, I would expect the migration to be quite minimal.
Unless, of course, you have lots of native queries using oracle-specific
sql constructs. If the app is pure hibernate, there's reasonable likelihood
that it will function with little more than changing the hibernate config.
Porting your schema will inevitably require a bit of work, though, again,
if your app is pure hibernate, you could start by simply allowing hibernate
to specify a schema for an empty db and then look at the differences
between the two for hints about what may need to change. I don't think
I've ever written an app of any maturity or complexity that was able to
exist entirely within native hibernate constructs, so you'll probably have
some work porting stored procs, recursive queries, and a few other odds and
ends that are different from one platform to the next, but the java
application code likely won't require much work at all once you sort that
stuff out. You'll also inevitably have a fair bit of db configuration
tuning ahead of you, as well, if your app stresses the hardware at all.
In response to
pgsql-jdbc by date
|Next:||From: Jeremy Whiting||Date: 2012-08-03 13:43:24|
|Subject: Re: Please consider using Gradle|
|Previous:||From: Dave Cramer||Date: 2012-08-03 10:22:52|
|Subject: Re: moving from oracle to postgresql|