3.4.e Installation - MySQL is missing

[piski]

Hi all,

I try to install the new 3.4.e to test Activiti preview and his abilities.

I begin the installation and I'm very surprised it don't propose me MySQL database !
I can only choose PostGRESQL  :cry:  … so :

1) Is this a choice to give up MySQL (and for future releases too) or is this an installation packaging mistake ?

2) If this is a mistake, how to overrid the issue ?

3) How upgrade our Alfresco 3.4.b with MySQL to Alfresco 3.4.e with POSTGRESQL ?

Thanks for your replies !

[mrogers]

You will need to do a "manual" install to use MySql.   

Given that you already have it that's just a trivial change to your alfresco-global.properties.

[piski]

Hello,

Thanks for your reply.

Will it be the case for future releases, Postgresql by default ?

[mrogers]

Yes.   We can't distribute mysql for legal reasons.

[piski]

So it will make sense to migrate to Postgresql to simplify next upgrades then !

According to you, Postgresql is more fast / reliable than MySQL, at least for Alfresco solution ?

[mrogers]

No.   There is no need to migrate from one to the other.    I suggest you keep running with what you are already familiar with.

[kjameson]

I am running Ubuntu 10.4 server … Alfresco 3.4.d … MYSQL …
I too was shocked to see the latest Alfresco with no MYSQL … I
could get no info as to why? I agree that it would make sense
to migrate to POSTGRESQL … problem is I hate to re-type all
data … so … Is there an "Alfresco approved" method / procedure
to migrate old data to POSTGRESQL … I attempted a manual
install of MYSQL over 3.4.e … swapping out WAR files … and there
is no MYSQL … the installers make such a nice clean install … everything
is in one place … the manual install would have POSTGRESQL in the
/opt/Alfresco-3.4.e area & MYSQLin the Ubuntu area … a bit confusing
and "hacked up" … I spent hours doing manual installs … never got it to run.
I too would really like to move  toward where ALFRESCO is apparently
moving … POSTGRESQL …Any info will be greatly appreciated!

KMJ

[mrogers]

For 3.4d to 3.4e   Shutdown,  Bbackup - just in case.
Replace the alfresco.war and share.war files with the new version.  
Restart.

[kjameson]

What about AWE.WAR / WCMQS.WAR ???
The above procedure works … if you are only using alfresco / share wars …
I couldn't get it to work if system has all 4 wars …

Apparently the switch is due to legal issues … re: MYSQL …
but nobody wants to share … does Alfresco have a plan to migrate
from MYSQL to POSTGRESQL …??? If so … how??
I'd prefer to make that kind of a move … before I have a million documents …
I'm (sort of) content with 3.4.d … but 3.4.e is definitely more stable …
(I have no need for Activiti) the old work flow seems OK (for my use)

Thanks again … KMJ

[stevericker]

Just to add to the conversation, for what it's worth, I've been digging into what a migration/conversion from MySQL to PostgreSQL would take.  It is not trivial, and there does not seem to be any automated way of doing it.  The alfresco schema should be fairly generic (ANSI compliant?) but here were some notes from someone that did this:

http://issues.alfresco.com/jira/browse/ALF-7896

I agree that the installer makes life so much easier.  Unfortunately, we've got lots of data already, so it seems like we're faced with the migration from MySQL to Postgres at some point?  It seems like simply replacing the .war files won't be enough for major upgrades?

What we've been doing as upgrades came out was a dump and restore for the database while copying over alf_data all into a freshly installed (recently via the installer) version.  If we want to keep doing it this way, again, the migration seems inevitable. 

Because of this, could someone share any experiences they've had with such a migration?  Or, alternatively, does anyone know of any Alfresco nuances in terms of its compliance with SQL "standards?"  Thanks.