ASP.Net MVC上传文件至数据库：插入时byte[]字段为空求代码排查

Hey there, let's break down why your byte[] field is ending up as null when inserting into the database. I'll walk through the most common culprits to check step by step:

First, make sure your byte[] data exists before it even reaches the DAL. If you're handling file uploads (e.g., in ASP.NET with IFormFile), double-check that you're properly reading the file stream into a byte array:

using var memoryStream = new MemoryStream();
await uploadedFile.CopyToAsync(memoryStream);
var fileBytes = memoryStream.ToArray();

Add a breakpoint or log statement right after this conversion to confirm fileBytes isn't null and has a valid length (>0). It's easy for this step to fail silently if the upload isn't processed correctly.

Next, ensure the byte[] property in your model isn't being overwritten or lost during transit from the controller to the DAL:

• Confirm your model class has a properly accessible property (getter and setter):

  public class YourModel
  {
      // Avoid readonly properties or logic that resets this value
      public byte[] FileData { get; set; }
  }
  

• Verify you're passing the model's FileData property correctly to your DAL's insert method. A common mistake is passing a null parameter instead of the actual byte array.

If you're using an ORM like EF Core, confirm the entity-to-database mapping is correct for your varbinary(3600) field:

• Use Fluent API to explicitly map the property (to avoid implicit mismatches):

  modelBuilder.Entity<YourEntity>()
      .Property(e => e.FileData)
      .HasColumnType("varbinary(3600)")
      .IsRequired(false); // Adjust to IsRequired(true) if the field shouldn't be null
  

If you're using raw SQL or Dapper, check that your INSERT statement includes the FileData field and that you're binding the parameter correctly:

• Bad example (missing the field):

  INSERT INTO YourTable (OtherField) VALUES (@OtherField)
  

• Good example:

  INSERT INTO YourTable (OtherField, FileData) VALUES (@OtherField, @FileData)
  

Even though you defined the field as varbinary(3600), verify your byte array isn't exceeding this length. Some databases will silently truncate or null out data that exceeds the field's size limit. Try temporarily changing the field to varbinary(MAX) to test if this is the issue.
Also, confirm the database field allows null values. If it's set to NOT NULL but your code is passing a null, you'd get an error—but if it allows nulls, that's a clue your upstream data isn't reaching the insertion step.

You mentioned the flow includes a DAL confirmation before insertion. Double-check this step isn't modifying the byte[] property accidentally. Add breakpoints before and after the confirmation logic to compare the FileData value—sometimes validation or cleanup code can inadvertently set the property to null.

Start with the earliest step (file conversion) and work your way down the pipeline; this will help you pinpoint exactly where the data is being lost.

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