如何在Laravel 5.*中向MSSQL的varbinary(max)字段插入图片数据

Hey Greg, let's sort out that SQL Server conversion error you're hitting. The problem is straightforward: you're trying to store a hexadecimal string (generated via unpack("H*", ...)) into a varbinary(max) field, and SQL Server blocks implicit conversion from nvarchar to varbinary types.

The Simple Solution: Store Raw Binary Data #

Instead of converting the image to a hex string, save the raw binary content of the file directly. Laravel's Eloquent handles binding binary data correctly for MSSQL, so this skips the invalid implicit conversion entirely.

Here's how to adjust your controller code:

public function store(Request $request) {
    $vorname = $request->input('vorname');
    $nachname = $request->input('nachname');
    $file = $request->file('avatar');
    
    // Optional: Keep storing the file on disk if you need it later
    $extension = $file->clientExtension();
    $fullname = $nachname . "_" . $vorname . "." . $extension;
    $file->storeAs('avatars' , $fullname);

    // Get raw binary content directly from the uploaded file (no need to read from disk again)
    $imageData = $file->get();

    Mitarbeiter::create([
        'PersonalNr' => request('personalnr'),
        'Mitarbeiterschluessel' => request('mitarbeiterkey'),
        'Vorname' => $vorname,
        'Familienname' => $nachname,
        'Bild' => $imageData // Store raw binary data directly
    ]);

    return view('welcome');
}

Key Improvements: #

• Removed unpack("H*", ...) and file_get_contents($path): Using $file->get() pulls binary content directly from the uploaded file, which is more efficient than writing to disk then reading back.
• The raw binary data is passed straight to the Bild field, so Eloquent handles the correct parameter binding for varbinary(max) automatically.

If You Must Use Hexadecimal Strings (Not Recommended) #

If you have a specific reason to work with hex strings, you need to explicitly convert them to varbinary in your query using CONVERT. Always use parameter binding to avoid SQL injection:

// After generating $imageData[1] as you originally did
Mitarbeiter::create([
    'PersonalNr' => request('personalnr'),
    'Mitarbeiterschluessel' => request('mitarbeiterkey'),
    'Vorname' => $vorname,
    'Familienname' => $nachname,
    'Bild' => DB::raw("CONVERT(varbinary(max), ?, 2)", [$imageData[1]])
]);

The 2 in CONVERT tells SQL Server to interpret the input as a hexadecimal string.

Why This Works #

SQL Server requires explicit conversion between string and binary types when the conversion isn't trivial. By passing raw binary data, you let Laravel handle the low-level type mapping, which eliminates the conversion error entirely.

内容的提问来源于stack exchange，提问作者Greg Ostry