Or do you suggest any better solution? There's no need to use uuid. The main issue here is how to prevent exposing of autoincrement primary keys...
Dne čtvrtek 16. ledna 2020 15:52:54 UTC+1 Petr Kaleta napsal(a): > > Hello, > on API I am currently working on, one of the requirements is, that auto > increment primary keys should not be exposed through public API. The reason > is not a security because access level is controlled on business logic but > to prevent basic analysis like "how many resources is there etc...). What > is your suggested solution for this? > > I thought about keeping standard autoincreased primary keys (for > performance and overall simplicity reasons) and add uuid column. Put index > on it and in models use your uuid plugin. Then create with_uuid and > with_uuid! dataset method to easily load models with uuid... > > What do you think? > > Thank you > > Petr > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/9f55f763-7452-4a51-9ea4-1e88c55461ac%40googlegroups.com.
