The mailing list for listmasters using Sympa

[Miles Fidelman <address@concealed>]

Being an existing Oracle customer, plus politics - that makes sense.

Thanks for the info.

Miles

Amos wrote:
> Personally I would be inclined to remain.  I've always had a bit of a 
> preference towards PostgreSQL.  However, the enterprise DBA group 
> where I work only supports Oracle, MSSQL, and MySQL.  Since we're not 
> really supposed to be running dbs and letting the DBA group handle 
> that, have to migrate it to MySQL.  So, basically politics.  ;-)
>
> Anyway, as to my original message, I discovered that this primary key 
> already existed, so the complaint was because the upgrade script tried 
> to create an index that was already there.  So for some reason it 
> wasn't able to detect the presence of this index.
>
>
>
> On Mon, Oct 27, 2014 at 11:37 AM, Miles Fidelman 
> <address@concealed <mailto:address@concealed>> wrote:
>
>     Any particular reason WHY you're migrating?
>
>     Given Oracle's acquisition of MySQL, it seems like most people are
>     moving the other way, or at least from MySQL to the Mariadb fork
>     of MySQL.
>
>     I'm kind of curious why you're migrating TO MySQL.
>
>     Regards,
>
>     Miles Fidelman
>
>         
> ------------------------------------------------------------------------
>         *De :* address@concealed
>         <mailto:address@concealed>
>         [mailto:address@concealed
>         <mailto:address@concealed>] *De la part
>         de* Amos
>         *Envoyé :* vendredi 24 octobre 2014 22:35
>         *À :* address@concealed
>         <mailto:address@concealed>
>         *Objet :* [sympa-users] migrating db from postgresql to mysql
>
>         It was decided that the db should be migrated from PostgreSQL
>         to MySQL.  The DBA team imported the data from the PostgreSQL
>         db into MySQL.  I then proceeded to bring up Sympa 6.1.23.
>
>         Overall things go well.  Sympa updates the db structure to
>         match the mysql settings.  However, the following error
>         message is logged:
>
>
>         Oct 24 15:23:20 localhost sympa[27509]: err
>         Upgrade::probe_db() Could not set field
>         'robot_subscriber,list_subscriber,user_subscriber' as PRIMARY
>         KEY, table'subscriber_table'.
>
>
>         Is this serious, anything to worry about?  Should something be
>         done manually?