Kirby, You have a good point. However, in this use case I am dealing with a jewelry store buying gold at their "market" rate. It is not the same as owning gold and the value changes based on a published (ie available through an API) rate. The jewelry store market rate for gold changes slowly, and from store to store So, I found creating a table called constants in the database allows me to change the value as needed and not have to touch the app code.
Mark On Mon, Feb 17, 2014 at 10:20 AM, C. Kirby <[email protected]> wrote: > I would suggest that your example, the price of gold, isn't a constant. If > you want to treat it as such then I agree with the above answers. However, > you could also look around for APIs that publish commodities values and > actually pull the real values in real (or semi real) time. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-users. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/236a1a12-151d-4730-af8c-c5cdc30a0287%40googlegroups.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAEqej2MR1Q0Dqe%2BFEkzSjgZaxDKnN1RFesHh64G3iyyp8gaSxA%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
