SQLSTATE[23000]: Integrity constraint violation: 4025 CONSTRAINT
Question
Hey I have problem when I insert my data from laravel to MySQL with error SQLSTATE[23000]: Integrity constraint violation: 4025 CONSTRAINT
Here is store controller
public function store(Request $request)
{
// $faker = Faker::create('id_ID');
$image = $request->file('Product_photo');
$extension = $image->getClientOriginalExtension();
$name = $request->Name;
$file_name = $name.'.'.$extension;
$image->move("images/listcar/", $file_name);
DB::table('car')
->insert([
//'id' => $faker->unique()->numberBetween($min = 0, $max = 200),
'product_photo' => $file_name,
'name' => $request->Name,
'production_year' => $request->Production_year,
'price' => $request->Price,
'merk' => $request->Merk,
'description' => $request->Description,
'varian' => $request->Variant,
'machine' =>$request->Machine,
'transmision' => $request->Transmision,
'wheel' => $request->Wheel,
]);
return redirect('/admin');
Here is my blade
<body>
<h1>Tambah Mobil</h1>
<div class="container">
<form action="/car/add" method="post" enctype="multipart/form-data">
{{ csrf_field() }}
<th>Nama</th><br>
<input type="text" name="Name" value=""><br/><br>
<th>Tahun Produksi</th><br>
<input type="text" name="Production_year" value=""><br/><br>
<th>Harga</th><br>
<input type="number" name="Price" value=""><br/><br>
<th>Select Product Image</th><br>
<input type="file" name="Product_photo" /><br/><br>
<th>Merek</th><br>
<input type="text" name="Merk" value=""><br/><br>
<th>Deskripsi</th><br>
<input type="textarea" name="Description" value=""><br/><br>
<th>Varian</th><br>
<input type="text" name="Variant" value=""><br/><br>
<th>Mesin</th><br>
<input type="text" name="Machine" value=""><br/><br>
<th>Transmisi</th><br>
<input type="text" name="Transmision" value=""><br/><br>
<th>Penggerak Roda</th><br>
<input type="text" name="Wheel" value=""><br/><br>
<br>
<input class="btn btn-primary" type="submit" value="Tambah Data Mobil">
</form>
<br>
<br>
</div>
MySQL structure
I really dont know where I went wrong, so please tell me if there is a wrong concepts
6 answers
solution1
3 2021-09-29 05:23:47
Change collation on mysql table - utf8mb4_general_ci: )
solution2
0 2021-07-05 14:48:20
Check you model $fillable array. Ensure all columns that records will be inserted are part of your $fillable
solution3
0 2022-06-17 14:49:04
i had same problem and solved:
if you save non-json into JSON field this error occurred like this:
$item = new WhatsAppWebhook($data);
$item->save();
return $item;
you need to encode
$payload = array("payload"=>json_encode($data));
$item = new WhatsAppWebhook($payload);
$item->save();
return $item;
solution4
0 2022-08-26 08:03:05
$user_role = array(('role')=>json_encode($request['role']));
$user_role = implode(', ', $user_role);
solution5
0 2022-10-22 14:21:09
I recently encountered a Laravel 'constraint violation' error related to JSON field. The logs were not revealing and the bug was intermittent. It took me some time, but fortunately the fix was easy.
TL;DR
- Problem: In Laravel's
Modelclass I had set the field to guarded and then provided an invalid default value. - Solution: In Laravel make the default values of your model's JSON fields valid JSON encoded strings. Even when they are empty
{}.
The Error
When I deployed code to the production environment for the first time, I saw a HTTP-500 error which had not arisen in my local testing:
[2022-09-27 03:54:27] local.ERROR: SQLSTATE[23000]: Integrity constraint violation:
4025 CONSTRAINT `table.field3` failed for `database`.`table` (SQL: insert into `table` (`field1`, `field2`, `field3`
...
#0 /path/to/project/vendor/laravel/framework/src/Illuminate/Database/Connection.php(719):
Illuminate\\Database\\Connection->runQueryCallback('insert into `ta...', Array, Object(Closure))
Not a very illuminating (pun intended) log entry, plus I could not reproduce the error in my vagrant development environment. The only difference between the vagrant box and production was that MariaDB was version 10.9 versus version 10.7 in production.
The Problem
It turns out the field type being json() in the Laravel migration was significant.
database/migrations/2022_09_25_133630_create_model_table.php:
new class extends Migration
{
public function up()
{
Schema::create('my_model', function (Blueprint $table) {
$table->id();
...
$table->json('field3');
I had always wondered why Laravel bothered with so many field types in the migration when they all got reduced to a handful once the SQL tables were created. In this instance the MariaDB column was longtext (non-nullable).
In Laravel's Model class I had set the field to guarded and then provided a default value which I thought was appropriate.
app/Models/my_model.php:
class my_model extends Model
{
use HasFactory;
/**
* The attributes that are NOT mass assignable.
*
* @var string[]
*/
protected $guarded = [
'field3'
];
/**
* Default values for attributes.
*
* @var array
*/
protected $attributes = [
'field3' => "",
];
It must be that the underlying mechanism of how the field was stored across the two versions of MariaDB came to the fore here? The error had arisen because an empty string which I had provided as a default value is not a valid JSON encoding and thus not compatible with the Laravel field type of json(). In my defense it is perfectly valid in the context of a non-nullable longtext column in MariaDB.
The Solution
In Laravel make the default values of your model's JSON fields valid JSON encoded strings.
app/Models/my_model.php:
class my_model extends Model
{
use HasFactory;
/**
* The attributes that are NOT mass assignable.
*
* @var string[]
*/
protected $guarded = [
'field3'
];
/**
* Default values for attributes.
*
* @var array
*/
protected $attributes = [
'field3' => "{}",
];
solution6
0 2022-11-25 02:55:49
This error may also occur in case a field that is not nullable and has no default value is left without value.
To fix this either add default values in your code or in your migraitons.
Here is a migration sample that updates email field to nullable and sets price default value to zero:
<?php
Schema::table('users', function (Blueprint $table) {
$table->string('email', 255)->nullable()->change();
$table->integer('price')->default(0)->change();
});
solution7
-1 2022-09-27 12:45:07
I also found that the root of the problem was with a bad default value for a field of type json().
Wrote about it on my blog here: https://www.dfoley.ie/blog/laravel-constraint-violation-error-on-json-field
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.