Hi Ravi, Functionality-wise, going from MySQL to Postgres is more of an update. I wouldn't expect too many probles this way. The other way round would have been a bit more tricky. The biggest trouble you might have is with stored procedure migration, in case you have any of those.
Also, Postgres ENUM type is more sophisticated, but quite different from MySQL's. If you had any enum columns, take special care with those. Other than that, just feel free to post any problems to the user group Cheers Lukas ---------- Forwarded message ---------- From: Ravi Shekhar <[email protected]> Date: 2011/7/14 Subject: Re: Hi! Please Help To: Lukas Eder <[email protected]> thanks .. that works.. i have updated the jooq version from 1.5.7 to 1.6.2 and in the process of conversion from MySQL to PostgreSQL. If there are some pointers to be careful about (in terms of transition from mysql to postgresql and its effect on Jooq layer) , please guide me on it. Thanks again! On Thu, Jul 14, 2011 at 9:19 PM, Lukas Eder <[email protected]> wrote: > > Hi Ravi, > > I gave you a hint on Stack Overflow... > > Cheers > Lukas -- Ravi.Shekhar --------------------------------------------
