Jump to content

Designing Suggestions


kostas

Recommended Posts

Hello everyone.

 

I am about to make an application that keeps track of stocks and other stuff for periods of time in order to produce graphs and present data.

The monitoring of the stocks should keep records of yesterday's values, a week before, month, 6 months and year.

I was wondering how i should go around this.

Should i create different tables for every period of time?

Or have one with all the values in it...

 

Any suggestions would be great appreciated.

 

Thanks in advance

Link to comment
Share on other sites

If putting them in one table increases the column count then there'e a flaw in your design.

 

See

http://dev.mysql.com/tech-resources/articles/intro-to-normalization.html

 

What are you proposing?

 

Well right now i have two tables.

One holds the [id], name and some other info of each stock

and the other holds the actual details of each stock which consists of 24 fields.

 

If i want to gather info for 5 different periods of time for those particular stocks, how it is possible

not to increase the column count without creating more tables ?

Sorry for the stupid questions, i am just beginning  ;D

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.