you forgot about FOO_BAR.
I think the right way would be to have a choice of name conversion
algorithms and you specify the one that suits your naming conventions with a
property in build.properties
fedor
> -----Original Message-----
> From: Byron Foster [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 06, 2001 12:54 PM
> To: turbine-dev
> Subject: Torque table and column naming
>
>
>
> Hello,
>
> I was wondering if it would useful to submit a patch that would
> change the behavior of how a table and column name is
> converted from the
> database xml schema to the java source name. Currently the
> behavior is so:
>
> foo_bar -> FooBar
> FooBar -> Foobar
> fooBar -> Foobar
>
> However, I thought it would be more intuitive to change the
> behavior to
> this:
>
> foo_bar -> FooBar
> FooBar -> FooBar
> fooBar -> FooBar
> Foobar -> Foobar
> foobar -> Foobar
>
> Formally, always capitalize first character. Always capitalize
> character after an underscore, remove underscores. Change
> nothing else.
>
> Java source names created by database names with underscores
> would not
> change under this new approach. But I think the added
> behavior is more
> intuitive. In general it seems to me that if I name a table
> "FooBar" I
> would like the class name to reflect the same, and not
> "Foobar". Same
> goes for the column names. The database xml names are
> significant since
> they may either be converted from database models, or output sql from
> torque may be used to create db models.
>
> Is this too much of a drastic change in naming? should this altered
> behavior be a property to be turned on?
>
> Thanks,
>
> Byron
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
