lack of support for non-primitive primary keys

I’m using uuids as primary keys, so they are stored in db as binary and in models as Buffer. I’ve overridden set() and toJSON() of the base model methods and it made it somewhat working, however there are still some bits of logic (especially in collections and maybe in relations) related to primary key comparison that basically does if(id === someOtherId) under the hood which obviously fails for Buffer keys.

Is there a plan on getting those bits fixed?

[ricardograca]

Yes, there’s #552, but I don’t think there’s any talk about that particular feature. Composite primary keys are very requested, but you’re actually the first person to request Buffer type primary keys.

I’m not sure it would be easy to implement, particularly when it comes to associations, so given the limited resources and the fact that no one makes any money for this work, it’s very unlikely that it will get implemented by someone that won’t be using that feature.

If it’s just a case of a few comparisons failing you may be able to dig into the source code and implement it yourself. The code is relatively clean, commented and easy to follow nowadays.

[adnanoner]

@helios1138 do you have an example of how you handle selects in your model? Got the parsing to work but not the selecting and formatting.