discoverSchema makes table lower camel case columns to be completely lowercase

[ariskemper]

Bug or feature request

• Bug
• Feature request

Description of feature (or steps to reproduce if bug)

1. Mysql table with camel case columns
2. Use discoverSchema to make json model

if table column name is for example zipCode, it will be named zipcode

Link to sample repo to reproduce issue (if bug)

Expected result

Properties part of json model schema

"emailVerified": {
  "type": "Boolean",
  "required": false,
  "length": null,
  "default": 0,
  "mysql": {
    "columnName": "emailVerified",
    "dataType": "tinyint",
    "dataLength": 1,
    "nullable": "Y"
  }
},

Actual result (if bug)

Properties part of json model schema

"emailverified": {
  "type": "Boolean",
  "required": false,
  "length": null,
  "default": 0,
  "mysql": {
    "columnName": "emailVerified",
    "dataType": "tinyint",
    "dataLength": 1,
    "nullable": "Y"
  }
},

Additional information (Node.js version, LoopBack version, etc)

Additional information (Node.js version, LoopBack version, etc)

Node.js: 6.9.2
loopback: 3.4.0
loopback-datasource-juggler: 3.2.0
loopback-connector-mysql: 3.0.0

[jannyHou]

Hi @ariskemper the dependency version has loopback-connector-mysql while your model.json file is using mssql as db specific config. I assume it's a typo but please make sure the config name is the identified to your connector.

@raymondfeng when user discovers a lower camel case property in mssql (e.g. emailVerified), loopback generates an all lowercase property in model (e.g. emailverified), even though the camel case name is mapped in db specific config. Could you confirm is it expected behavior or a bug? Thanks.

[jannyHou]

@raymondfeng Also users are interested in providing a custom naming convention in migration/discovery. details see issue: loopbackio/loopback-connector-mysql#57

Does loopback has its naming convention documented somewhere? Or any link of the strategy we can follow?
If not I am thinking of document it, therefore confirm the strategy with you first :)
And any thought about the suggestion "provide custom naming convention function"?

[ariskemper]

@jannyHou its not connector specific, because code in loopback-datasource-juggler does this.

[raymondfeng]

Please note that discoverSchema allows options.nameMapper to provide custom name mapping. See https://github.com/strongloop/loopback-datasource-juggler/blob/master/lib/datasource.js#L1304

[jannyHou]

@ariskemper please check comment #1268 (comment)
Will options.nameMapper solve your problem?

[ariskemper]

@raymondfeng @jannyHou i know, it provides options.nameMapper, but i think that camel case named columns should stay camel cased?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

[sureshkodur]

Hi, I have same issue. How can resolve this issue?

[agnes512]

please check #3343