On Mon, Apr 21, 2008 at 9:47 AM, Coey Minear
<cminear / securecomputing.com> wrote:

>  Probably the biggest issue will be resolving the conflict between what
>  'Mastering' and Rails use for conventions: singular vs. plural
>  entity/table names and natural vs. just-use-integer sequence primary
>  keys being the two biggest.  My advice would be to just use Rails'
>  conventions when you get to the implementation stage.  The point with
>  the techniques in 'Mastering' is that you get a good understanding of
>  your data before you start writing a bunch of code that assumes
>  something that will change drastically later.
>
>  Coey

I should mention that you can use your own table names in Rails, you
can have your own primary key, and you can fake your _multiple_
natural keys with the 'unique' constraint.  But it takes a little more
work, and is a little more problematic when fleshing out bugs.

It can be done though.  I wrote a small IT support db for Rails called
icanhazfix with table names like 'happiez' instead of 'users' with key
'kitteh', and 'naybrhud' instead of 'groups' with key 'famfam'.

Todd