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
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
David Pollak feeder.of.the.be...@gmail.com writes:
but I'm running into a problem with the test cases. Since the names of
the Mapped objects are fixed once determined, it's hard to reuse the
different models in MapperSpecs for the different naming conventions.
I was thinking about adding
On Thu, Jan 28, 2010 at 3:09 AM, Jeppe Nejsum Madsen je...@ingolfs.dkwrote:
David Pollak feeder.of.the.be...@gmail.com writes:
but I'm running into a problem with the test cases. Since the names of
the Mapped objects are fixed once determined, it's hard to reuse the
different models in
On Jan 26, 8:04 pm, Jeppe Nejsum Madsen je...@ingolfs.dk wrote:
I'v implemented this:
In MapperRules add
var columnName: String = String = s = s.toLowerCase
(and perhaps tableName, indexName etc. if we want full flexibility)
- name: object name unchanged (ie not lower cased)
-
On Wed, Jan 27, 2010 at 5:53 AM, Jeppe Nejsum Madsen je...@ingolfs.dkwrote:
On Jan 26, 8:04 pm, Jeppe Nejsum Madsen je...@ingolfs.dk wrote:
I'v implemented this:
In MapperRules add
var columnName: String = String = s = s.toLowerCase
(and perhaps tableName, indexName etc. if we
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
