Download the PHP package icedevelopment/mysql-workbench-schema-exporter without Composer

README

This is a fork from [https://github.com/johmue/mysql-workbench-schema-exporter](), in order to improve and cotinue its development, as it looks abandoned in the original repo :(

What is MySQL Workbench schema exporter?

The application is intended to create:

• Doctrine 1.0 YAML Schema
• Doctrine 2.0 YAML Schema and Annotation Classes
• Zend DbTable
• Zend Rest Controller
• Sencha ExtJS3 Model
• Propel XML Schema
• CakePHP (not implemented)

schema files from MySQL Workbench models (*.mwb). It is inspired by mysql-workbench-doctrine-plugin.

Doctrine behaviours

Support for behaviours is implemented for Doctrine1. Use the comment fields in tables.

{d:actAs}
  actAs:
    timestampable:
      [..]
{/d:actAs}

Foreign key name

To replace relations name by the name of the foreign key, start the foreign key name with "d:".

Command Line Interface (CLI)

There is a new CLI to simplify the export process named export.php, you can look under the cli folder. The CLI has feature to customize export configuration before exporting. By default, CLI application will use config file export.json located in the current directory to supply the parameter if it find it. To disable this behaviour, see the option below.

The syntax of CLI:

php cli/export.php [options] FILE [DEST]

Where:

• options:
  • --export=type, choose the result of the export, currently available types:
    • doctrine1-yaml, Doctrine 1.0 YAML schema
    • doctrine2-yaml, Doctrine 2.0 YAML schema
    • doctrine2-annotation, Doctrine 2.0 Annotation classes (default)
    • propel1-xml, Propel XML schema
    • zend-dbtable, Zend DbTable
    • zend-rest-controller, Zend Rest Controller
    • sencha-extjs3, Sencha ExtJS3 Model
  • --config=file, read export parameters from file (in JSON format)
  • --saveconfig, save export parameters to file export.json, later can be used as value for --config=file
  • --list-exporter, show all available exporter
  • --no-auto-config, disable automatic config file lookup
  • --zip, compress the result
  • --help, show the usage (or suppress any parameters)
• FILE, the mwb file to export
• DEST, the destination directory (optional), if not specified current directory assumed

Sample usage:

php cli/export.php --export=doctrine2-annotation example/data/test.mwb example/result

php cli/export.php --config=example/data/config.json example/data/test2.mwb example/result

Sample export paramaters (JSON) for doctrine2-annotation:

{
    "export": "doctrine2-annotation",
    "zip": false,
    "dir": "temp",
    "params": {
        "backupExistingFile": true,
        "skipPluralNameChecking": false,
        "enhanceManyToManyDetection": true,
        "bundleNamespace": "",
        "entityNamespace": "",
        "repositoryNamespace": "",
        "useAnnotationPrefix": "ORM\\",
        "useAutomaticRepository": false,
        "indentation": 4,
        "filename": "%entity%.%extension%",
        "quoteIdentifier": false,
        "propertyNameCodingStyle": "lowercamelcase",
        "tableNameCodingStyle": "underscore",
        "columnNameCodingStyle": "underscore"
    }
}

Coding style options:
* raw
* underscore
* uppercamelcase
* lowercamelcase

Exporter Options

General options

General options applied to all formatter.

• indentation

  The indentation size for generated code.

• useTabs

  Use tabs for indentation instead of spaces. Setting this option will ignore the indentation-option

• filename

  The output filename format, use the following tag %schema%, %table%, %entity%, and %extension% to allow the filename to be replaced with contextual data. Default is %entity%.%extension%.

• skipPluralNameChecking

  Skip checking the plural name of model and leave as is, useful for non English table names. Default is false.

• backupExistingFile

  If target already exists create a backup before replacing the content. Default is true.

• enhanceManyToManyDetection

  If enabled, many to many relations between tables will be added to generated code. Default is true.

Option list for Doctrine 1.0

• extendTableNameWithSchemaName

  Include schema name beside the table name. Default is false.

• {d:externalRelations}

Option list for Doctrine 2.0 YAML

• useAutomaticRepository

  Automatically generate entity repository class name.

• bundleNamespace

  The global namespace prefix for entity class name.

• entityNamespace

  The entity namespace. Default is Entity.

• tablePrefix Default is empty

  Define a prefix for tables name. Default is empty.

• repositoryNamespace

  The namespace prefix for entity repository class name. For this configuration to apply, useAutomaticRepository must be set to true.

• extendTableNameWithSchemaName

  Include schema name beside the table name. Default is false.

Option list for Doctrine 2.0 Annotation

• useAnnotationPrefix

  Doctrine annotation prefix. Default is ORM\.

• useAutomaticRepository

  See above.

• bundleNamespace

  See above.

• entityNamespace

  See above.

• tablePrefix Default is empty

  See above.

• repositoryNamespace

  See above.

• skipGetterAndSetter

  Don't generate columns getter and setter. Default is false.

• generateEntitySerialization

  Generate method __sleep() to include only real columns when entity is serialized. Default is true.

• quoteIdentifier

  If this option is enabled, all table names and column names will be quoted using backtick (`). Usefull when the table name or column name contains reserved word. Default is false.

• {d:m2m}false{/d:m2m}

  MySQL Workbench schema exporter tries to automatically guess which tables are many-to-many mapping tables and will not generate entity classes for these tables. A table is considered a mapping table, if it contains exactly two foreign keys to different tables and those tables are not many-to-many mapping tables.

  Sometimes this guessing is incorrect for you. But you can add a hint in the comment of the table, to show that it is no mapping table. Just use "{d:m2m}false{/d:m2m}" anywhere in the comment of the table.

• {d:unidirectional}true{/d:unidirectional}

  All foreign keys will result in a bidirectional relation by default. If you only want a unidirectional relation, add a flag to the comment of the foreign key.

• {d:owningSide}true{/d:owningSide}

  In a bi-directional many-to-many mapping table the owning side of the relation is randomly selected. If you add this hint to one foreign key of the m2m-table, you can define the owning side for Doctrine.

• {d:cascade}persist, merge, remove, detach, all{/d:cascade}

  You can specify Doctrine cascade options as a comment on a foreign key. The will be generated into the Annotation. (Reference)

• {d:fetch}EAGER{/d:fetch}

  You can specify the fetch type for relations in the comment of a foreign key. (EAGER or LAZY, doctrine default is LAZY)

• {d:orphanRemoval}true{/d:orphanRemoval}

  Another option you can set in the comments of foreign key. (Reference)

Option list for Propel Xml

• namespace
• addVendor

Option list for Zend DbTable

• tablePrefix
• parentTable
• generateDRI
• generateGetterSetter

Option list for Zend Rest Controller

• tablePrefix
• parentTable

Option list for Sencha ExtJS3 Model

• classPrefix
• parentClass

Requirements

Works with PHP 5.3 and up.

Links

• MySQL Workbench
• Doctrine Project
• Symfony Project

Test-Database

• Sakila DB *.mwb
• Sakila DB docs

Example