Skip to content

Commit

Permalink
Update src/main/asciidoc/reference/aerospike-object-mapping.adoc
Browse files Browse the repository at this point in the history
Co-authored-by: Ronen Botzer <[email protected]>
  • Loading branch information
agrgr and rbotzer authored Dec 24, 2024
1 parent 9caffce commit 1eca9f0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/main/asciidoc/reference/aerospike-object-mapping.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ The following description outlines what type of conversion, if any, will be done
* By default, the type of the field annotated with `@id` is turned into a `String` to be stored in Aerospike database.
If the original type cannot be persisted (see xref:#configuration.keep-original-key-types[keepOriginalKeyTypes]
for details), it must be convertible to `String` and will be stored in the database as such, then converted back to the original type when the object is read.
This is transparent to the application but needs to be considered if using external tools like `AQL` to view the data.
This is transparent to the application but needs to be considered if using external tools like `AQL` and the Aerospike JDBC Driver to view the data.
* If no field named "id" is present in the Java class then an implicit '_id' file will be generated by the driver but not mapped to a property or field of the Java class.

When querying and updating `AerospikeTemplate` will use the converter to handle conversions of the `Query` and `Update` objects that correspond to the above rules for saving documents so field names and types used in your queries will be able to match what is in your domain classes.
Expand Down

0 comments on commit 1eca9f0

Please sign in to comment.