Android Room无法保存Base64值至SQLite数据库求助

Let's break down the most likely causes for your missing base64Image field and walk through fixes step by step:

1. Double-Check Constructor & Getter/Setter Implementation #

This is the most common culprit when fields fail to persist in Room. Since you mentioned omitting these methods, make sure:

• Your constructor includes the base64Image parameter (otherwise, the field defaults to null when creating the object)
• Getters/Setters follow JavaBean naming conventions (Room relies on these to access fields)

Example of correct implementation:

// Constructor
public HealthCareWorkersInformation(long hcwId, String base64Image) {
    this.hcwId = hcwId;
    this.base64Image = base64Image;
    this.updatedAt = new SimpleDateFormat("dd MM yyyy, HH:mm", Locale.getDefault()).format(Calendar.getInstance().getTime());
}

// Getter & Setter
public String getBase64Image() {
    return base64Image;
}

public void setBase64Image(String base64Image) {
    this.base64Image = base64Image;
}

2. Validate Column Name Mapping #

Room automatically converts camelCase field names to snake_case column names (e.g., base64Image → base64_image). While SQLite is case-insensitive, explicit column naming can eliminate mapping ambiguity:

@ColumnInfo(name = "base64_image") // Or "base64Image" if you prefer exact matching
private String base64Image;

3. Check for Truncated or Invalid Base64 Data #

Your test JSON includes a very long Base64 string. Before inserting, verify the string is complete:

// Add this right before inserting to confirm the data exists
Log.d("HCW_DEBUG", "Base64 length: " + healthCareWorkersInformation.getBase64Image().length());

If the length is 0 or unexpectedly short, your JSON parser might be truncating the string during deserialization.

4. Inspect the SQLite Database Directly #

Use Android Studio's Device File Explorer to pull your database file (located at data/data/[your-package-name]/databases/). Open it with a SQLite browser to check if the base64_image column actually contains data:

• If the column is empty: The issue is during insertion (likely missing constructor/setter)
• If the column has data: The issue is during retrieval (check getter method or Room query mapping)

5. Consider Using BLOB for More Efficient Storage #

Storing Base64 as a string is inefficient—you can save space and avoid potential string-length issues by using a BLOB instead:

@ColumnInfo(typeAffinity = ColumnInfo.BLOB)
private byte[] imageBlob;

// When inserting:
String base64Str = yourJsonData.getBase64Image();
// Strip the "data:image/png;base64," prefix first
String pureBase64 = base64Str.substring(base64Str.indexOf(",") + 1);
byte[] imageBytes = Base64.decode(pureBase64, Base64.DEFAULT);
healthCareWorkersInformation.setImageBlob(imageBytes);

// When retrieving:
byte[] imageBytes = healthCareWorkersInformation.getImageBlob();
String base64Str = "data:image/png;base64," + Base64.encodeToString(imageBytes, Base64.DEFAULT);

6. Verify JSON Deserialization #

If you're using a library like Gson to convert the test JSON to your entity, ensure the base64Image field is mapped correctly. Add a @SerializedName annotation if there's any naming mismatch:

@SerializedName("base64Image")
private String base64Image;

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