id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
34569	Unify all model fields to call get_prep_value from get_db_prep_value	Julie Rymer	stimver	"Following on #34539, should all fields that do not currently call `get_prep_value` from `get_db_prep_value` be updated to call it so that we have no more inconsistency with the [https://docs.djangoproject.com/en/4.2/howto/custom-model-fields/#converting-python-objects-to-query-values fields customization doc]?

Here is the list of all concerned fieldst:
- AreaField (contrib.gis)
- DistanceField (contrib.gis)
- ArrayField (contrib.postgres)
- DurationField
- UUIDField (this one even has a definition for `get_prep_value`, but it is never called)
- ForeignKey (like previous one, possess definition for `get_prep_value`, never called)

Please give me your thoughts or if I missed anything.
I for one am in favour of harmonising all field to follow the field API

(PS: wasn't sure about what ticket type this should be classified as)"	Cleanup/optimization	assigned	Database layer (models, ORM)	4.2	Normal			Florian Demmer	Accepted	0	0	0	0	0	0