fix: add enum values to MySQL object of property decorator

[aaqilniz]

Checklist

• DCO (Developer Certificate of Origin) signed in all commits
• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• API Documentation in code was updated
• Documentation in /docs/site was updated
• Affected artifact templates in packages/cli were updated
• Affected example projects in examples/* were updated

👉 Check out how to submit a PR 👈

[coveralls]

Pull Request Test Coverage Report for Build 9876716776

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 54.772%

---

Totals
Change from base Build 9858607965:	0.0%
Covered Lines:	9566
Relevant Lines:	12465

---

💛 - Coveralls

[dhmlau]

@samarpanB, since you work with the mysql connector closely, could you please take a look at this PR? Thanks.

[samarpan-b]

Okay

[samarpanB]

@aaqilniz can you please link it with an issue ? That ways we can understand what exact problem its resolving.

[dhmlau]

@aaqilniz, thanks for the PR. Sorry that it's taking so long to have this reviewed.
I'm wondering if it fits better to have this discovery code in the MySQL connector.

[dhmlau]

There's acceptance in https://github.com/loopbackio/loopback-next/tree/master/acceptance/repository-mysql. It might be better to keep the database/connector specific tests there.

[aaqilniz]

Hi, @dhmlau. I have moved this change to loopbackio/loopback-datasource-juggler#2420.

I think adding these changes here is not a good idea. This might cause problems for other connectors.

I have added these changes where this db-specific field (mysql, postgresql or memory) is already being added in the above PR.