我正在使用 Symfony 2.8 和 Doctrine，并且我将 security.yml 配置为指向实现UserInterface的User类。我的 ORM 架构在 YAML 中。
问题： - 在数据库中，用户还指定了“电子邮件”字段，登录用户的 Symfony 没有填写该字段，并且“密码”字段为空。
当我这样做时$this->get('doctrine.orm.entity_manager')->clear(User::class);
，实体管理器正在正确获取实体。但是当实体来自会话时，它是不正确的。
问题还在于，当我尝试在存储库上使用 find() 从数据库中获取新实体时，当我不使用$em->clear(User::class)
问题： - 如何告诉 Symfony/Doctrine 以这样的方式构建我的实体，它将所有字段都填满，所以它会变得可持久化？
<?php
namespace XXX\AppBundle\Model\Entity;
use XXX\AppBundle\Model\Entity\Server\Logging;
use Doctrine\ORM\Mapping as ORM;
use Symfony\Component\Security\Core\User\UserInterface;
/**
* User
*/
class User implements UserInterface
{
/**
* @var integer $id
*/
protected $id;
/**
* @var string $username
*/
protected $username;
/**
* @var string $email
*/
protected $email;
/**
* @var string $password
*/
protected $password;
/**
* @var array $roles
*/
protected $roles = array();
/**
* @var \Doctrine\Common\Collections\Collection $logEvents
*/
protected $logEvents;
/**
* @return int
*/
public function getId()
{
return $this->id;
}
/**
* {@inheritdoc}
*/
public function getUsername()
{
return $this->username;
}
/**
* @param string $username
* @return $this
*/
public function setUsername($username)
{
$this->username = $username;
return $this;
}
/**
* @return string
*/
public function getEmail()
{
return $this->email;
}
/**
* @param string $email
* @return $this
*/
public function setEmail($email)
{
$this->email = $email;
return $this;
}
/**
* {@inheritdoc}
*/
public function getPassword()
{
return $this->password;
}
/**
* @param string $password
* @return $this
*/
public function setPassword($password)
{
$this->password = $password;
return $this;
}
/**
* Returns the roles or permissions granted to the user for security.
*/
public function getRoles()
{
$roles = $this->roles;
// guarantees that a user always has at least one role for security
if (empty($roles)) {
$roles[] = 'ROLE_USER';
}
return array_unique($roles);
}
public function setRoles(array $roles)
{
$this->roles = $roles;
}
/**
* Returns the salt that was originally used to encode the password.
*/
public function getSalt()
{
// See "Do you need to use a Salt?" at http://symfony.com/doc/current/cookbook/security/entity_provider.html
// we're using bcrypt in security.yml to encode the password, so
// the salt value is built-in and you don't have to generate one
return;
}
/**
* Removes sensitive data from the user.
*/
public function eraseCredentials()
{
$this->password = null;
$this->email = null;
}
/**
* Appends an entry to administration log
*
* @param \XXX\AppBundle\Model\Entity\Server\Logging $logEvent
* @return $this
*/
public function appendLog(Server\Logging $logEvent)
{
if (!$this->logEvents->contains($logEvent))
{
$this->logEvents->add($logEvent);
}
return $this;
}
/**
* Remove a log entry from the history
*
* @param \XXX\AppBundle\Model\Entity\Server\Logging $logEvent
* @return $this
*/
public function clearLogEntry(Server\Logging $logEvent)
{
$this->logEvents->removeElement($logEvent);
return $this;
}
}
和ORM配置：
XXX\AppBundle\Model\Entity\User:
type: entity
table: users
repositoryClass: XXX\AppBundle\Model\Repository\UserRepository
id:
id:
type: integer
scale: 0
length: null
unique: false
nullable: false
precision: 0
id: true
generator:
strategy: IDENTITY
fields:
username:
type: string
scale: 0
length: null
unique: true
nullable: false
precision: 0
email:
type: string
scale: 0
length: null
unique: true
nullable: false
precision: 0
password:
type: string
scale: 0
length: null
unique: false
nullable: false
precision: 0
roles:
type: json_array
scale: 0
length: null
unique: false
nullable: false
precision: 0
oneToMany:
logEvents:
targetEntity: XXX\AppBundle\Model\Entity\Server\Logging
cascade:
- remove
- persist
fetch: LAZY
mappedBy: author
inversedBy: null
orphanRemoval: false
orderBy: null
lifecycleCallbacks: { }
感谢您的时间。祝你有美好的一天 ：-）