ewrayjohnson

> A workaround would be to specify a "valid" column name in the `@property` decorator. See https://github.com/dhmlau/loopback4-example-todo-customized#if-i-have-a-table-name-or-column-name-that-is-different-from-the-model-name-and-property-what-should-i-change for an example. Thanks.

For those of us that have not taken the leap to LoopBack 4, the @property decorator is not an option. Instead we would have to use postgresql.columnName

> @ewrayjohnson, would you be interested to submit a PR? Yes

Cannot do a Fiddle/Codepen right now. However, here is a simple example model (a combo box _might_ work) : ``` { "animals": ["cat", "dog", "frog"] } ```

Composite keys/indexes are use for other than the primary key. This feature was instrumental on apps I delivered using LB3 for performance and uniqueness constraints. With LB3 no longer supported,...

Did you ever get a solution to this?

Yes, it appears to be working now.