Nicolas M.

@ljharb Thanks for your feedback. Maybe I am missing something here, but I guess everything should be transparent, and the one-to-one match between proxy methods traps and Reflect API should...

@allardmuis That makes sense now, thanks for clarification. This explanation should definitely go into the documentation. > I cannot update the docs I guess one possibility is to submit a...

> Uh, thanks, but I would appreciate some discussion upfront before sending such a PR :] Note that (as you already found) there are existing issues, all of them are...

I guess this relates to issue #5807. But strictly speaking, it is not an issue with enums themselves. It is an issue of having identically named properties (each property having...

> Oh, you have different field names there, I missed that part. @B4nan Yes that's the point I underline with my example. Even with different fieldnames, things do not work...

> Good point. Maybe we could even have an object in the first parameter, it would have both table name and schema name as properties, and a `quoted` (or `quotedName`?)...

f3a5702 brings the implementation of the `expression` callback now accepting two parameters: - first parameter `table` is an object containing 3 properties: - `name` is the name of the table...

All right, all good now ! Thanks for having brought fresh eyes on this. The reason of my initial confusion stems from `@Check` decorator, which is explicitly requiring to pass...

> The inference in those decorators is rather new addition, and its incompatible with the explicitly provided type argument, IIRC I left the check decorator as is since it felt...

The platform-specific quoting is now implemented. Added tests for various platforms to make sure the platform-specific quoting is indeed respected by the `@Index` or `@Unique` expressions. Also types have been...