Propel2: `deleted` column conflicts with propels own `deleted` attribute
Let’s say we have a table user
with the following column:
<column name="deleted" type="CHAR" sqlType="enum(....)"/>
The generated object model will now look like this:
/**
* The value for the deleted field.
* @var string
*/
protected $deleted;
But propel already generated a property with the same name for internal use:
/**
* attribute to determine whether this object has been deleted.
* @var boolean
*/
protected $deleted = false;
Which results in Fatal error: Cannot redeclare User::$deleted in /Base/User.php on line xxx
Propel should warn us about this conflict; or even better should not name internal properties with general names (maybe add a prefix?).
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Comments: 39 (26 by maintainers)
@marcj Any idea when this branch will be ready for production?