So far, the only database that is officially supported is SQL Server, but you may still use Xomega with other databases with some database related features being not fully functional. Here is a list of problems I foresee and ways to work around them.
1. Import from Database generator will most likely not work. You can obviously always define the model manually from scratch, but this could be pretty tedious. You can also try to import your database into a SQL server database for the sake of importing it into the model and then switch back to MySQL.
2. Once you have the model imported (or manually defined), you should be able to generate the Entity Data Model, which may work with MySQL out of the box. If it doesn't, then you can always import the EDM directly from MySQL using Visual Studio.
3. Generation of the script to update a database based on the model changes will likely not work. You would have to either manually track the changes to the database, or use the standard Microsoft migrations mechanism.
4. All other generators for the UI forms, view models (Xomega data objects), services, etc. should be fully functional and can help you quickly develop high quality multi-tier applications.
We're not aware of any other similar (open source) projects for MySQL, but Xomega is based on a unique and innovative technology, which you will unlikely to find in other products. If you decide to give Xomega a try, please don't hesitate to contact us with any questions or issues.