blocks|key|1263434|text|唯一验证规则允许忽略给定的ID，在您的示例中，该ID是您正在更新的数据集的ID。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1263435|'email'+=>+'unique:users,email_address,10'|code-block|syntax|javascript|1263436|http://four.laravel.com/docs/validation#rule-unique|offset|length|1263437|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|1F|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|T|8|@]|9|@$I|U|J|V|1|W]]|A|$]]|$1|K|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|H]]]]

The unique validation rule allows to ignore a given ID, which in your case is the ID of the data set you are updating.

<pre><code>'email' =&gt; 'unique:users,email_address,10'
</code></pre>

<a href="http://four.laravel.com/docs/validation#rule-unique" rel="noreferrer">http://four.laravel.com/docs/validation#rule-unique</a>

blocks|key|1263443|text|请参阅http://four.laravel.com/docs/validation#rule-unique上的文档|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1263444|您可以排除用户自己的id|1263445|protected+$rules=+[
++++'name'++++=>+'required',
++++'email'++++=>+[
++++++++'required',
++++++++'unique:user,email,THE_USERS_USER_ID',
++++++++'email'
++++]
];|code-block|syntax|javascript|1263446|entityMap|0|LINK|mutability|MUTABLE|url|http://four.laravel.com/docs/validation#rule-unique^0|3|1F|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

See the documentation on <a href="http://four.laravel.com/docs/validation#rule-unique" rel="nofollow">http://four.laravel.com/docs/validation#rule-unique</a>

You can exclude the users own id 

<pre><code>protected $rules= [
 'name' =&gt; 'required',
 'email' =&gt; [
 'required',
 'unique:user,email,THE_USERS_USER_ID',
 'email'
 ]
];
</code></pre>

blocks|key|1263473|text|我在我的验证器函数中处理这类事情。我的validators数组被设置为类变量。然后我会这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1263474|public+function+validate()+
{
++++//exclude+the+current+user+id+from+'unqiue'+validators
++++if(+$this->id+>+0+)
++++{
++++++++$usernameUnique+=+'unique:users,username,'.$this->id;
++++++++$emailUnique+=+'unique:users,email,'.$this->id;
++++++++$apiUnique+=+'unique:users,api_key,'.$this->id;
++++}
++++else
++++{
++++++++$usernameUnique+=+'unique:users,username';
++++++++$emailUnique+=+'unique:users,email';
++++++++$apiUnique+=+'unique:users,api_key';
++++}

++++$this->validators['username']+=+array('required',+'max:32',+$usernameUnique);
++++$this->validators['email']+=+array('required',+'max:32',+$emailUnique);
++++$this->validators['api_key']+=+array('required',+'max:32',+$apiUnique);

++++$val+=+Validator::make($this->attributes,+$this->validators);

++++if+($val->fails())
++++{
++++++++throw+new+ValidationException($val);
++++}
}|code-block|syntax|javascript|1263475|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I handle this sort of thing in my validator function. My validators array is setup as a class variable. I then do something like this:

<pre><code>public function validate() 
{
 //exclude the current user id from 'unqiue' validators
 if( $this-&gt;id &gt; 0 )
 {
 $usernameUnique = 'unique:users,username,'.$this-&gt;id;
 $emailUnique = 'unique:users,email,'.$this-&gt;id;
 $apiUnique = 'unique:users,api_key,'.$this-&gt;id;
 }
 else
 {
 $usernameUnique = 'unique:users,username';
 $emailUnique = 'unique:users,email';
 $apiUnique = 'unique:users,api_key';
 }

 $this-&gt;validators['username'] = array('required', 'max:32', $usernameUnique);
 $this-&gt;validators['email'] = array('required', 'max:32', $emailUnique);
 $this-&gt;validators['api_key'] = array('required', 'max:32', $apiUnique);

 $val = Validator::make($this-&gt;attributes, $this-&gt;validators);

 if ($val-&gt;fails())
 {
 throw new ValidationException($val);
 }
}
</code></pre>

blocks|key|314080|text|一种方法是在模型中创建一个验证函数，并在控制器传入输入、场景和id+(要忽略)的情况下调用它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|314081|public+function+validate($input,+$scenario,+$id+=+null)
{
++++$rules+=+[];

++++switch($scenario)
++++{
++++++++case+'store':
++++++++++++$rules+++=+[
++++++++++++++++'name'+++++=>+'required%7Cmin:5%7Cunique:users',
++++++++++++++++'email'++++=>+'required%7Cemail%7Cunique:users',
++++++++++++++++'password'+=>+'required%7Cmin:4%7Cconfirmed'
++++++++++++];
++++++++++++break;

++++++++case+'update';
++++++++++++$rules+++=+[
++++++++++++++++'name'+++++=>+'required%7Cmin:5%7Cunique:users'+.',name,'+.+$id,
++++++++++++++++'email'++++=>+'required%7Cemail%7Cunique:users'+.',email,'+.+$id,
++++++++++++++++'password'+=>+'min:4%7Cconfirmed'
++++++++++++];
++++++++++++break;
++++}

++++return+Validator::make($input,+$rules);
}|code-block|syntax|javascript|314082|然后在控制器中：|314083|++++$input++++++=+Input::all();
++++$validation+=+$user->validate($input,+'update',+$user->id);

++++if+($validation->fails())
++++{
++++++++//+Do+stuff
++++}
++++else
++++{
++++++++//+Validation+passes
++++++++//+Do+other+stuff
++++}|314084|正如其他人提到的，唯一规则的第三个参数指定了要忽略的id。您可以添加其他用例，例如“login”以重用验证函数。|314085|或者，Jeffrey+Way在Tuts+Premium+has+a+great+series+of+lessons+in+"What's+New+In+Laravel+4"，其中包括一些使用服务和侦听器处理验证的其他方法。|offset|length|314086|entityMap|0|LINK|mutability|MUTABLE|url|https://tutsplus.com/course/whats-new-in-laravel-4/#validation^0|0|0|0|0|0|F|1Z|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@$O|14|P|15|1|16]]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

One approach is to create a validation function in the model and call it with the controller passing in the input, scenario and id (to ignore).

<pre><code>public function validate($input, $scenario, $id = null)
{
 $rules = [];

 switch($scenario)
 {
 case 'store':
 $rules = [
 'name' =&gt; 'required|min:5|unique:users',
 'email' =&gt; 'required|email|unique:users',
 'password' =&gt; 'required|min:4|confirmed'
 ];
 break;

 case 'update';
 $rules = [
 'name' =&gt; 'required|min:5|unique:users' .',name,' . $id,
 'email' =&gt; 'required|email|unique:users' .',email,' . $id,
 'password' =&gt; 'min:4|confirmed'
 ];
 break;
 }

 return Validator::make($input, $rules);
}
</code></pre>

Then in the controller:

<pre><code> $input = Input::all();
 $validation = $user-&gt;validate($input, 'update', $user-&gt;id);

 if ($validation-&gt;fails())
 {
 // Do stuff
 }
 else
 {
 // Validation passes
 // Do other stuff
 }
</code></pre>

As others mentioned, the 3rd parameter of the unique rule specifies an id to ignore. You can add other cases, such as 'login' to reuse the validation function.

Alternatively, Jeffrey Way at <a href="https://tutsplus.com/course/whats-new-in-laravel-4/#validation" rel="nofollow">Tuts Premium has a great series of lessons in "What's New In Laravel 4"</a> which includes a couple of other approaches to handling validation using services and listeners.

blocks|key|314103|text|从2014-01-14开始，你可以使用sometimes属性，我相信泰勒在2天前将它们添加到了Laravel+4.1中|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|314104|$v+=+Validator::make($data,+array(
++++'email'+=>+'sometimes%7Crequired%7Cemail',
));|code-block|syntax|javascript|314105|sometimes仅验证存在的输入。如果您没有insert的默认值，这可能适合您的场景，也可能不适合您的场景。|314106|http://laravel.com/docs/validation#conditionally-adding-rules|314107|entityMap|0|LINK|mutability|MUTABLE|url^0|0|B|J|9|0|0|0|9|0|0|1P|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|11|8|@]|E|@]|F|$J|K]]|$1|L|3|M|5|6|7|12|8|@$9|13|A|14|B|D]]|E|@]|F|$]]|$1|N|3|O|5|6|7|15|8|@]|E|@$9|16|A|17|1|18]]|F|$]]|$1|P|3|-4|5|6|7|19|8|@]|E|@]|F|$]]]|Q|$R|$5|S|T|U|F|$V|O]]]]

As of 2014-01-14, you can use <code>sometimes</code> attribute, I believe Taylor added them 2 days ago to Laravel 4.1

<pre><code>$v = Validator::make($data, array(
 'email' =&gt; 'sometimes|required|email',
));
</code></pre>

<code>sometimes</code> only validate input if it exists. this may or may not suit your exact scenario, if you don't have a default value for insert.

<a href="http://laravel.com/docs/validation#conditionally-adding-rules" rel="nofollow">http://laravel.com/docs/validation#conditionally-adding-rules</a>

blocks|key|314933|text|我已经通过在需要更新和创建的模型上使用不同的规则来解决这个问题，比如用户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|314934|我有一个扩展Eloquent的模型类，我在其中定义验证，然后所有扩展模型的子模型都可以定义$rules和$update_rules。如果仅定义$rules，则它将同时用于创建和更新。|offset|length|style|BOLD|314935|class+Model+extends+Eloquent+{
++++protected+$errors;
++++protected+static+$rules+=+array();++++
++++protected+$validator;

++++public+function+__construct(array+$attributes+=+array(),+Validator+$validator+=+null)+{
++++++++parent::__construct($attributes);++++
++++++++$this->validator+=+$validator+?:+\App::make('validator');
++++}

++++protected+static+function+boot()+{
++++++++parent::boot();

++++++++#+call+validatie+when+createing
++++++++static::creating(function($model)+{
++++++++++++return+$model->validate();
++++++++});

++++++++#+call+validatie+when+updating+with+$is_update+=+true+param
++++++++static::updating(function($model)+{
++++++++++++return+$model->validate(true);
++++++++});
++++}

++++public+function+validate($is_update+=+false)+{
++++++++#+if+we+have+$update_rules+defined+in+the+child+model,+and+save+is+an+update
++++++++if+($is_update+and+isset(static::$update_rules))+{
++++++++++++$v+=+$this->validator->make($this->attributes,+static::$update_rules);
++++++++}
++++++++else+{
++++++++++++$v+=+$this->validator->make($this->attributes,+static::$rules);
++++++++}

++++++++if+($v->passes())+{
++++++++++++return+true;
++++++++}

++++++++$this->setErrors($v->messages());
++++++++return+false;
++++}

++++protected+function+setErrors($errors)+{
++++++++$this->errors+=+$errors;
++++}

++++public+function+getErrors()+{
++++++++return+$this->errors;
++++}

++++public+function+hasErrors()+{
++++++++return+!+empty($this->errors);
++++}
}|code-block|syntax|javascript|314936|entityMap^0|0|19|6|1G|D|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

I have solved this by having different rules for update and create on models that need to do so, like Users.

I have a Model class that extends Eloquent, where I define the validation, and then all child models that extend the Model can have have both the $rules and $update_rules defined. If you define only $rules, it will be used both for create and update.

<pre><code>class Model extends Eloquent {
 protected $errors;
 protected static $rules = array(); 
 protected $validator;

 public function __construct(array $attributes = array(), Validator $validator = null) {
 parent::__construct($attributes); 
 $this-&gt;validator = $validator ?: \App::make('validator');
 }

 protected static function boot() {
 parent::boot();

 # call validatie when createing
 static::creating(function($model) {
 return $model-&gt;validate();
 });

 # call validatie when updating with $is_update = true param
 static::updating(function($model) {
 return $model-&gt;validate(true);
 });
 }

 public function validate($is_update = false) {
 # if we have $update_rules defined in the child model, and save is an update
 if ($is_update and isset(static::$update_rules)) {
 $v = $this-&gt;validator-&gt;make($this-&gt;attributes, static::$update_rules);
 }
 else {
 $v = $this-&gt;validator-&gt;make($this-&gt;attributes, static::$rules);
 }

 if ($v-&gt;passes()) {
 return true;
 }

 $this-&gt;setErrors($v-&gt;messages());
 return false;
 }

 protected function setErrors($errors) {
 $this-&gt;errors = $errors;
 }

 public function getErrors() {
 return $this-&gt;errors;
 }

 public function hasErrors() {
 return ! empty($this-&gt;errors);
 }
}
</code></pre>

I use the following rules for validation on creating a new user:

<pre><code>protected $rules= [
 'name' =&gt; 'required',
 'email' =&gt; [
 'required',
 'unique:user',
 'email'
 ]
];
</code></pre>

When updating an existing user I use the same ruleset as shown above
but don't want a validation error if the user didn't change his email at all.

I currently resolve this by using the following:

<pre><code>if (!User::changed('email')) {
 unset($user-&gt;email);
}
</code></pre>

It feels like a dirty workaround to me so I was wondering if there are better alternatives.

Also note that the <code>changed</code> method is something I wrote myself. Does anyone know if there
is a native Laravel 4 method for checking whether a model property has changed?

Thanks!

Laravel 4 Validation

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在创建新用户时，我使用以下规则进行验证：protected $rules= [    'name'    => 'required',    'email'    => [        'required',        'unique:user',        'email'    ]];在更新现有用户时，我使...

问Laravel 4验证
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Laravel 4验证EN