[Nitro] [PATCH][BUGFIX] Camel cases in class names are nothandled correctly

TRANS transfire at gmail.com
Thu Apr 6 13:41:15 EDT 2006


On 4/6/06, itsme213 <itsme213 at hotmail.com> wrote:
>
> "Bryan Soto" <bryan.a.soto at gmail.com> wrote in message
>
> > We really need to structure things better. There should be only one
> > place names are created.
>
> <disclaimer> don't have in-depth knowledge of code base </disclaimer>
>
> Would it not be be better if all the og macros simply recorded the meta-data
> without any database code decisions?
>
> The database (or other) code can be generated at the end. Name ambiguities,
> short names, inferrable names (e.g. inverses and foreign keys), etc. can all
> be done most effectively at that point.

Well put. That's exaclty the direction I've been trying to encouge.

T.




More information about the Nitro-general mailing list