Thoughts on "createdByUserLogin" field taking id-vlong (String VARCHAR(255))

[Ashish Vijaywargiya]

Hello,


For ex. few reference are :
createdByUserLogin field in MarketingCampaign entity.
dontCancelSetUserLogin in OrderItem entity.


Thanks in Advance.

--
Ashish Vijaywargiya

Yesterday I was reviewing few entities, then I realized that we are using "id-vlong" for the fields acting as foreign key & referring to the "userLoginId" of the UserLogin table. "id-vlong" = VARCHAR(255) is too much space for saving the userLoginId. At max I can think of userLoginId to be of length of 25 or 30. If there is any specific reason for keeping it of this much length then please share your thoughts on this.

smime.p7s
Description: S/MIME Cryptographic Signature