Accounting package model naming

Rails
1

Hello everyone,

I’m a native French speaker, and I’m struggling with some model names.
I’m working on the accounting package for an app. I have Accounts
and TransactionRecords, and now I must relate accounts with
transactions. What should the model between be named ?

I thought of AffectedAccount, RecordMember, TransactionMember, but
none of these feels very satisfactory. Even in French I’m not sure
how I would name these objects…

So, if anybody found a good solution, I’d be interested in hearing it.

Thanks !

François Beausoleil
http://blog.teksol.info/
http://piston.rubyforge.org/

2

Hi Francois,

Francois B. wrote:

I’m working on the accounting package for an app.
I have Accounts and TransactionRecords, and now
I must relate accounts with transactions. What
should the model between be named ?

I’m not completely sure I understand your question, but perhaps this
will
help.

If you are asking about naming the models for your tables…

Models in Rails are, by convention, named the singular version of the
name
of the table on which they are based. The model for your Accounts table
should be named Account. The model for TransactionRecords should be
named
TransactionRecord.

If you are asking about naming a model that relates ‘accounts with
transactions’, without more information I’m not sure why you would want
a
seperate model for this. It seems like a simple has_namy / belongs_to
relationship would work. If not, please say more.

Sorry I couldn’t be more help.

Best regards,
Bill

3

On Oct 19, 2006, at 6:08 AM, Francois B. wrote:

I’m a native French speaker, and I’m struggling with some model names.
I’m working on the accounting package for an app. I have Accounts
and TransactionRecords, and now I must relate accounts with
transactions. What should the model between be named ?

I thought of AffectedAccount, RecordMember, TransactionMember, but
none of these feels very satisfactory. Even in French I’m not sure
how I would name these objects…

I would think:

Accounts->TransactionRecords->Ledgers

–
– Tom M., CTO
– Engine Y., Ruby on Rails Hosting
– Reliability, Ease of Use, Scalability
– (866) 518-YARD (9273)

4

Hello Tom,

2006/10/19, Tom M. [email protected]:

Accounts->TransactionRecords->Ledgers

Ah! Bingo, exactly what I wanted.

Thanks !

François Beausoleil
http://blog.teksol.info/
http://piston.rubyforge.org/

5

Perhaps not very useful in this case but I find looking up a thesaurus
to be
very useful in coming up with good model names sometimes.

Hammed

6

On 10/19/06, Tom M. [email protected] wrote:

how I would name these objects…

I would think:

Accounts->TransactionRecords->Ledgers

Sounds pretty similar to what we’re doing here (though our naming is a
bit off, we inherited some made-up-english terms), but could you
elaborate on what each table contains?

Accounts is straight forward enough. But, if someone else store the
accounts for different entities (we call them ‘clients’) in one db,
I’d love to see how you tie accounts to reporting.

I’m not sure about TxRecord vs. Ledger, though.

Isak