Lift Mapper (Record) camelCase to snake_case for case insensitive databases
Please make the Scala identifier to database identifier translation convention dependent on whether the database supports case sensitive or case insensitive identifiers.
For example, Hibernate offers an Enhanced Naming Convention that translates Java camelCase to a more Oracle friendly snake_case. I am interested in doing the same thing with Lift Mapper/
Record. In the mean time, I need to override dbTableName and dbColumnName, but I'd like to avoid that and just agree on the convention.
I could imagine that the Database Provider would maintain a flag to say whether the database is case sensitive or not, and then based on that flag, would pass either the camelCase directly (for case sensitive), or snake_case(camelCase) (for case insensitive).
I am specifically using Lift Mapper with Oracle, but I think this issue relates to Lift Record too as well as any other case insensitive database.
See discussion: http://groups.google.com/group/liftweb/t/e7f85ede13b303da
For example, Hibernate offers an Enhanced Naming Convention that translates Java camelCase to a more Oracle friendly snake_case. I am interested in doing the same thing with Lift Mapper/
Record. In the mean time, I need to override dbTableName and dbColumnName, but I'd like to avoid that and just agree on the convention.
I could imagine that the Database Provider would maintain a flag to say whether the database is case sensitive or not, and then based on that flag, would pass either the camelCase directly (for case sensitive), or snake_case(camelCase) (for case insensitive).
I am specifically using Lift Mapper with Oracle, but I think this issue relates to Lift Record too as well as any other case insensitive database.
See discussion: http://groups.google.com/group/liftweb/t/e7f85ede13b303da
Leave a comment
on 2010-02-06 19:49 *
By github.importer
Imported from GitHub: http://github.com/dpp/liftweb/issues/155/find