Alzabo and MySQL
This documentation is about what special support Alzabo has for MySQL, as well as what is lacking.
MySQL support is based on the 3.23.* release series, with some support for features that are starting to appear in the 4.0.* releases. Earlier versions of MySQL will probably work with Alzabo, though Alzabo cannot magically make these releases support new features like fulltext indexes.
selectmethods of either table or schema objects.
Because Alzabo knows about this, it will ignore these defaults when reverse engineering an RDBMS.
Again, Alzabo ignores these lengths when reverse engineering a schema.
< Alzabo::Create::Schema-sync_backend|Alzabo::Create::Schema/``sync_backend'' >> or
< Alzabo::Create::Schema-sync_backend_sql|Alzabo::Create::Schema/``sync_backend_sql'' >> methods. If you are using this feature from the web based schema creator, you will see that even immediately after running the
sync_backendmethod, Alzabo may still think there are differences between the two schemas. This is not a problem, as running the SQL Alzabo generates will not actually change your database.
Alzabo will try to use transactions whenever appropriate. Unfortunately, there is no way to determine whether or not a given table supports transactions so Alzabo simply sets AutoCommit to 0, whether or not this will actually do anything.
As of now, there is no way to specify table specific attributes with Alzabo.