1 Replies - 135 Views - Last Post: 16 June 2019 - 07:55 PM Rate Topic: -----

#1 compuco   User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 1
  • Joined: 16-June 19

Naming Convention Help

Posted 16 June 2019 - 01:51 PM

Hi all,

I have a question on how you guys would handle this scenario. I have 4 tables as such: estimates, estimate_features, estimate_feature_stories and estimate_feature_story_tasks ; from the naming you can see that tasks are many -> one to stories, stories are many -> one to features and features are many -> one of estimates. Well maybe not obvious without an ERD but this is the setup. It is basically an estimate module for an agile project where we use features, stories and tasks. But as you can see these names are getting quite long and what if we added another layer like estimate_feature_story_task_comments... and so on ; how would you go about naming these in the real world as to be descriptive but also not going crazy overboard on table and key lengths?

I also have to access these from a web MVC back end and front end and will also have to have model classes, views and controllers for these tables but that is another question I'll ask in another category.

Thanks for any insight!

Is This A Good Question/Topic? 0
  • +

Replies To: Naming Convention Help

#2 modi123_1   User is online

  • Suitor #2
  • member icon



Reputation: 15226
  • View blog
  • Posts: 60,944
  • Joined: 12-June 08

Re: Naming Convention Help

Posted 16 June 2019 - 07:55 PM

I don't know - seems like this is being built the wrong way.

Stories would be the top.
Stories have tasks
Stories have features.

A single story would have a single estimate.
A task would have an estimate.

A story could have comments.

All of these would be tables with relational tables between them on keys.
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1