-
useAutomaticRepository
, (*6)
Automatically generate entity repository class name., (*7)
-
bundleNamespace
, (*8)
The global namespace prefix for entity class name., (*9)
-
entityNamespace
, (*10)
The entity namespace., (*11)
Default is Entity
., (*12)
-
repositoryNamespace
, (*13)
The namespace prefix for entity repository class name. For this configuration to apply,
useAutomaticRepository
must be set to true
., (*14)
-
skipColumnWithRelation
, (*15)
Don't generate columns definition (for YAML) or columns variable and columns getter and setter
(for Annotation) which has relation to other table., (*16)
Default is false
., (*17)
-
relatedVarNameFormat
, (*18)
The format for generated related column name., (*19)
Default is %name%%related%
., (*20)
-
nullableAttribute
, (*21)
How nullable attribute of columns and joins is generated. Set to auto
if you want to
automatically include nullable attribute based on its value. Set to always
to always
include nullable attribute., (*22)
Default is auto
., (*23)
-
generatedValueStrategy
, (*24)
The stragety for auto-generated values., (*25)
Default is auto
., (*26)
-
defaultCascade
, (*27)
The default cascade option to define., (*28)
Default is false
., (*29)
-
useAnnotationPrefix
, (*33)
Doctrine annotation prefix., (*34)
Default is ORM\
., (*35)
-
skipGetterAndSetter
, (*36)
Don't generate columns getter and setter., (*37)
Default is false
., (*38)
-
generateEntitySerialization
, (*39)
Generate method __sleep()
to include only real columns when entity is serialized., (*40)
Default is true
., (*41)
-
generateExtendableEntity
, (*42)
Generate two class for each tables in schema, one for base and one other for extend class.
The extend class would not be generated if it already exist. So it is safe to place custom code
inside the extend class., (*43)
This option will generate entity using Single Table Inheritance., (*44)
Default is false
., (*45)
-
quoteIdentifierStrategy
, (*46)
This option determine wheter identifier quoting is applied or not, depend on the strategy
value., (*47)
-
auto
, indentifier quoting enabled if identifier is a reserved word.
-
always
, always quote identifier.
-
none
, never quote identifier.
Default is auto
., (*48)
-
extendsClass
, (*49)
This option allows you to define a base class from which all generated entities extend., (*50)
Default is ''
., (*51)
-
propertyTypehint
, (*52)
This option allows you to specify whether type-hinting should be enabled for all non-scalar properties
whose type is a class. E.g. \DateTime
would be type-hinted but not object
or string
., (*53)
Default is false
., (*54)
-
{d:bundleNamespace}AcmeBundle{/d:bundleNamespace}
(applied to Table), (*55)
Override bundleNamespace
option., (*56)
-
{d:m2m}false{/d:m2m}
(applied to Table), (*57)
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., (*58)
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., (*59)
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., (*60)
-
{d:unidirectional}true{/d:unidirectional}
(applied to ForeignKey), (*61)
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., (*62)
-
{d:owningSide}true{/d:owningSide}
(applied to ForeignKey), (*63)
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., (*64)
-
{d:cascade}persist, merge, remove, detach, all{/d:cascade}
(applied to ForeignKey), (*65)
You can specify Doctrine cascade options as a comment on a foreign key. They will be generated
into the Annotation.
(Reference), (*66)
-
{d:fetch}EAGER{/d:fetch}
(applied to ForeignKey), (*67)
You can specify the fetch type for relations in the comment of a foreign key. (EAGER or LAZY,
doctrine default is LAZY), (*68)
-
{d:orphanRemoval}true{/d:orphanRemoval}
(applied to ForeignKey), (*69)
Another option you can set in the comments of foreign key.
(Reference), (*70)
-
{d:order}column{/d:order}
(applied to ForeignKey), (*71)
Apply OrderBy annotation to One To Many and Many To Many relation. OrderBy annotation can be
written in the following format:, (*72)
column[,(asc|desc)]
Multiple columns are supported, separated by line break. Example usage:, (*73)
{d:order}
column1
column1,desc
{/d:order}
Doctrine 2.0 Annotation with ZF2 Input Filter Classes formatter directly extend Doctrine 2.0
Annotation. The setup options and model comment behavior exactly the same as Doctrine 2.0
Annotation with the following addons., (*74)