commit
ae1c171392
@ -49,7 +49,7 @@ entities:
|
||||
const STATUS_VISIBLE = 'visible';
|
||||
const STATUS_INVISIBLE = 'invisible';
|
||||
|
||||
/** @Column(type="varchar") */
|
||||
/** @Column(type="string") */
|
||||
private $status;
|
||||
|
||||
public function setStatus($status)
|
||||
@ -70,7 +70,7 @@ the **columnDefinition** attribute.
|
||||
/** @Entity */
|
||||
class Article
|
||||
{
|
||||
/** @Column(type="varchar", columnDefinition="ENUM('visible', 'invisible')") */
|
||||
/** @Column(type="string", columnDefinition="ENUM('visible', 'invisible')") */
|
||||
private $status;
|
||||
}
|
||||
|
||||
|
@ -348,7 +348,7 @@ This is an **execute one-time** command. It should not be necessary for
|
||||
you to call this method multiple times, escpecially when using the ``--from-database``
|
||||
flag.
|
||||
|
||||
Converting an existing databsae schema into mapping files only solves about 70-80%
|
||||
Converting an existing database schema into mapping files only solves about 70-80%
|
||||
of the necessary mapping information. Additionally the detection from an existing
|
||||
database cannot detect inverse associations, inheritance types,
|
||||
entities with foreign keys as primary keys and many of the
|
||||
|
Loading…
Reference in New Issue
Block a user