Byron Foster <[EMAIL PROTECTED]> writes:
> Daniel Rall wrote:
>
> >FWIW, I added code in Turbine 3 for this sort thing.
> >
> >
>
> Hello, Here is a new patch that implements the java naming scheme
> through attributes in the database schema that works with the new code
> that you added. the <database> element now has a new attribute
> "defaultNameConversion" that may be either "underscore", "javaname",
> or "nochange". The description of these are in the DTD. Also the
> <table> and <column> elements have an optional attribute
> "nameConversion" that may also be one of the above. Without any
> method specification the behavior of the name conversion is as it was
> before.
Commited, thanks Byron. Would you explain the addition of the
nameConversion attribute to the id-method-parameter element? Also,
since this change is Java-specific (I think), IMO an attribute name
which includes the text "java" for the database element's default Java
naming scheme would be more descriptive than defaultConversionMethod
(which is rather generic). How about defaultJavaNamingMethod (or
something like that)?
Daniel
p.s. 4 character indent in the future, please
(http://jakarta.apache.org/turbine/common/code-standards.html).
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
