A design question, my RATE table looks something like this.... SQL> desc rate Name Null? Type ------------------------------------------------------------------------ -------- ----------------- RATE_CODE NOT NULL CHAR(2) RATE_EFFECTIVE_START_DATE NOT NULL DATE RATE_EFFECTIVE_END_DATE NOT NULL DATE . .
those are the PK fields...and the SQL to query the table is easy. I am trying to determine if I can "tighten up" the table, like this... SQL> desc rate Name Null? Type ------------------------------------------------------------------------ -------- ----------------- RATE_CODE NOT NULL CHAR(2) RATE_EFFECTIVE_DATE NOT NULL DATE I just haven't been able to code the right SQL. Has anyone else taken this approach? Sorry for these design questions, I am just being very anal about every table, PK column and index, before we dive into development and everything becomes "hard coded". TIA!!!! Chris -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Grabowy, Chris INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
