Hi Phil Yep, it looks like that will do.
Thanks >> -----Original Message----- >> From: freedc....@gmail.com [mailto:freedc....@gmail.com] On Behalf Of >> Phil >> Sent: 10 May 2010 13:53 >> To: mysql@lists.mysql.com >> Subject: Re: Database tables for Exchange rates >> >> For the exchange rates only you don't really need more than one table. I >> work with an enterprise financial system and we have exchange rate tables >> which are updated with data every day. >> >> Something like >> >> BASE_CURR char(3) >> NONBASE_CURR char(3) >> EFF_DATE DATE >> EXCH_RATE DECIMAL(15,6) -- or however much precision you need >> >> We have other columns storing tolerances but that should be enough. First >> 3 >> columns are your key. >> >> Separate tables for the currency codes themselves. >> >> On Mon, May 10, 2010 at 7:28 AM, Mimi Cafe <mimic...@googlemail.com> >> wrote: >> >> > I am designing a database to store exchange rates and other >> information. >> > The >> > tables fro the exchange rates will store exchange rates fro all >> currencies. >> > >> > Can I have any suggestions about the number of tables to use for the >> > exchange rate? I think I will need at least 2 tables, but I am looking >> for >> > suggestions on how to achieve maximum speed when querying the database >> and >> > also avoid redundant tables or rows. >> > >> > Mimi >> > >> > >> > -- >> > MySQL General Mailing List >> > For list archives: http://lists.mysql.com/mysql >> > To unsubscribe: >> http://lists.mysql.com/mysql?unsub=pchap...@nc.rr.com >> > >> > >> >> >> -- >> Distributed Computing stats >> http://stats.free-dc.org -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
