ee if I can add some documentation for
methods that need some, beginning with some easy ones.
Best Regards,
--
Frederick Ros aka Sleeper -- [EMAIL PROTECTED]
Don't sacrifice clarity for small gains in "efficiency".
- The Elements of Programming Style (Kernighan & Pl
t preoperly indented to transform it into
verbatim).
I wrote several patches regarding these but so far it seems that none
have been integrated. Perhaps that having a separate trac category for
this kind of fixes would help in order to sort out these simple patches.
--
Frederick Ros aka Sleeper -- [
Frederick Ros wrote :
| Hi,
|
| I'm currently using Rails with a legacy database that uses it's own
| naming conventions, one of them being that names are CamelCased.
|
| To be consistent I tried to CamelCase also my HABTM association names
| like:
|
|has_and_belongs_to_m
sily fixed by prepending a self to the
#{reflection.name} for example, and this is what is done in the patch
attached to ticket #4823.
Best Regards,
--
Frederick Ros aka Sleeper -- [EMAIL PROTECTED]
"All language designers are arrogant. Goes with the territory..."
(By Larry Wall)
it, than nothing and nowhere to click for editing.
Best Regards,
--
Frederick Ros aka Sleeper -- [EMAIL PROTECTED]
Use uniform input formats.
- The Elements of Programming Style (Kernighan & Plaugher)
pgpZ9rwlJwMOS.pgp
Description: PGP signature
__
.
However all the generated fixtures are still generated using the id
primary key. I created a (more than) very small patch
(http://dev.rubyonrails.org/ticket/4343) that allow to fix this, using
the fact that all the templates are preprocessed through Erb.
Best Regards,
--
Frederick Ros aka Sleeper
