Workaround to circumvent a bug in EOSchemaSynchronization when adding columns to an existing table

There seems to be a bug in com.webobjects.eoaccess.EOSchemaSynchronization and since it has been deprecated, I made a workaround and some minor changes to the column creation method. I am not sure if this bug only surfaces when adding columns to an existing table, but it surely happens when I try to use migrations and add a column after a table has been created. It's been tested only with MySQL.