aw <anth...@whitford.com> writes: > Would it make sense to have the ConnectionIdentifier play a role? > (Including DefaultConnectionIdentifier.) > > Because, for me, the decision to use snake_case or camelCase depends > on the capabilities of the database. If I have an application with > multiple database connections, the decision for snake_case or > camelCase is not universal.
Not sure what your use case is here: 1) A single mapped object can exist in different dbs? 2) Different mapped objects can exists in different dbs? With the current design, 1) is not possible. Once the name of a field has been determined, it'll stay fixed. 2) Might be doable if we add the connection identifier as parameter to the function that decides the names. In general, I don't think we should be too smart about this. There will probably always be scenarios that can fail, in which case you can manually override the name (except in 1) above :-) /Jeppe -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
