I am planning to create a pricing matrix for a project in Rails. It’s supposed to be a table of destinations and departure locations, and prices depending on where you came and are planning to go.
I am kinda undecided on how to better do this: either making a table in the db for this matrix, or making a mega array of constants. Problem is, the client should be able to edit this matrix so its most likely going the database route.
Anyhow, what’s a good schema for this? Destination id, Departure id, then price? destination and departure ids will be foreign keys for a table containing all possible locations. Is there a better way of doing this?
Make it a db table.
The only thing constant about prices is that they change.
Added:
Pricing (also called product factoring) is something that I have a lot of experience with.
Your clients may also ask/or appreciate added pricing tools to help them get things right. Eg, your sw:
You may also need to worry about effective dates for the pricing. Ie how to roll-out a new set of prices in a co-ordinated way.