API Expert
Jan 2, 2023

--

The problem here is that you are creating a hardcoded ID... one that has to be converted to the TYPE (ie id.toLong()). This means that it is more a NATURAL KEY than a primary (read issues with 'Natural keys')

Thus it is not being protected from duplication, synchronized with the other keys and can potentially even pull up false/innacurate records

What you SHOULD be doing is searching on an INDEX instead (if you want to try somnething like this)

--

--

API Expert
API Expert

Written by API Expert

Owen Rubel is the 'API Expert'. He is an Original Amazon team member, Creator of API Chaining(R), Leader in API Automation

Responses (1)