How to manage item price in data base

Question

1.00/5 (1 vote)

See more:

I have two table in my application, one is "item" and "itemprice" and these are already created by a previous developer. The itemprice table contain fields like, unitOfSale , itemPoint, itemSalePrice and itemPurchasePrice, tax. There are some fields those are duplicate in item and itmPrice table.

Can i merge itemPrice table in item table. will it do any negative imapact on architecture,

Do I need to keep the history of itemprice when it changes?

If I need to keep history of price then which architecture should i follow ? one table (merged table) or two table?

What I have tried:

I did not tried it any more as it specific condition

Posted 19-Mar-18 0:16am

Asif_Aziz

Updated 19-Mar-18 0:53am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2018-03-19T00:55:00

I'd suggest that there are two tables so that the price can change: if an item is bought on Monday at £10, and returned on Thursday after the price rose to £15, you want to refund the right amount of money.
There are two ways to handle that: one is to keep the price charged with the receipt / invoice item line data, and the other is to maintain a separate table entry for each change in item price.
From a quick look at your table, I'd say that the receipt / invoice data is your second table but you'd have to inspect the rest of the table and the code that manipulates it to be sure - we can't do that for you, we don't have any access to it. But if it is, then I'd strongly recommend you leave it as is!