Loading...

XML

Word

Printable

JSON

Documentation Changes:
Needed
Documentation Changes Summary:

Hide

1. What would you like to communicate to the user about this feature?

The _safeContent_ field cannot be read or written from the model classes.

2. Would you like the user to see examples of the syntax and/or executable code and its output?

3. Which versions of the driver/connector does this apply to?

Laravel-MongoDB 5.12.0

Show
1. What would you like to communicate to the user about this feature? The _ safeContent _ field cannot be read or written from the model classes. 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to? Laravel-MongoDB 5.12.0

Hide the reserved _safeContent_ field from Queryable Encryption query results, at the hydration level, instead of on the model.

The server writes _safeContent_ into encrypted documents. It is an implementation detail and should not appear in application results.
Filter _safeContent_ when hydrating query results, covering both Eloquent models and raw reads (query builder, DB collection reads, aggregation).
The write guard stays: the field cannot be set or unset on a model.
This was removed from the Queryable Encryption PR to keep the model layer untouched; this ticket adds the filtering at the results level.

is depended on by

PHPLIB-1972 Hide the reserved __safeContent__ field from query results

related to

PHPLARA-50 Queryable Encryption integration in Laravel-MongoDB

Hide the reserved safeContent field from query results