Dimitry.

>>
>>I find singular more convenient.
>>
>

I Think it is a little more complex than this. On a large Database it is a great maintenence advantage to easily group child tables with the Parent For instance. You can have a table called User for a list of users. Great. If you store all of the user preferences in a table called UserPreference, and a table for user state stored in a table called UserState, and a table that contains user access rights for variious things stored in a table called UserAccess, then all of these tables are always grouped together in the database when you want to look at them. When you have 60 or 70 or a hundred tables this is a major convenience. Going all over the database to look into relevent tables is a pain in the neck.

Maybe a better example I have is this. I have in one application a full Policy model and a full Investment tracking model, each with around 10 or so supporting table. By using a good naming convention, children having double names, I can have almost all of them (not quite all) grouped by relationship.

Final thought:
Parent = Singular Name,
Child = Double Name
GrandChild = More.

Regards,