RE: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-15 Thread Robson, Peter
Yes - the right answer. And can be validated with a little basic normalisation. peter edinburgh Thinking about Matt's question, would it be proper to move the column to a EMP_TERMINATED table with an outer join on EMPNO? There wouldn’t be any NULLs... Rich Rich Jesse

RE: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-15 Thread Toepke, Kevin M
'); -Original Message-From: Grabowy, Chris [mailto:[EMAIL PROTECTED]]Sent: Monday, October 14, 2002 5:11 PMTo: Multiple recipients of list ORACLE-LSubject: RE: No Nulls? (was: Warehouse design: snowflake vs star schem Hmmm...but what about the index? Which is faster? select * from

RE: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Jesse, Rich
Hey Dick, Thanks for your response. The reason I ask the question is because I *wish* our ERP system supported NULLs, at least in date fields. To properly explain why, I need to preface it with a short explanation: Our 3rd party ERP system is one that was designed in the '80s using indexed

RE: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread DENNIS WILLIAMS
Rich If you were to give each of your developers a pop quiz on nulls, how many do you think would pass? I agree with Dick, that nulls are a confusing concept that usually only the DBA really understands. I feel that an important decision when beginning a new application is whether or not to

RE: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Adams, Matthew (GECP, MABG, 088130)
Title: RE: No Nulls? (was: Warehouse design: snowflake vs star schem No application that I can reasonably think of should use NULLS, except those pre-81 where there are obsolete columns. Everytime somebody says this to me, I ask them: How do you handle still employed employees

Re: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Igor Neyman
Title: RE: No Nulls? (was: Warehouse design: snowflake vs star schem END_EMPLOYEMENT date for still employed employees equals to "01/01/4000" (or any other pre-defined date in distant future). Igor Neyman, OCP DBA[EMAIL PROTECTED] - Original Message - From

RE: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Fink, Dan
Title: RE: No Nulls? (was: Warehouse design: snowflake vs star schem The problem I see with NO NULLS is that artificial data must be created, where the data is truly not known. Whether you deal with NULLs or artificial data, you will always have to code accordingly, so it is a wash. Igor's

Re: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Marc Perkowitz
Title: RE: No Nulls? (was: Warehouse design: snowflake vs star schem I disagree with the use of "dummy" values to represent missing data. It reminds me of the olden days when we coded in 12/31/99 and such. Shades of COBOL HIGH-VALUES! You're introducing a lot of dependenci

Re: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Igor Neyman
Title: RE: No Nulls? (was: Warehouse design: snowflake vs star schem Or you'll have to explain to the HR manager why all of the employees appear to be terminated! they aren't terminated! at least not yet :-) Igor Neyman, OCP DBA[EMAIL PROTECTED] - Original Message - From

RE: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Grabowy, Chris
49 PMTo: Multiple recipients of list ORACLE-LSubject: RE: No Nulls? (was: Warehouse design: snowflake vs star schem The problem I see with NO NULLS is that artificial data must be created, where the data is truly not known. Whether you deal with NULLs or artificial data, you will always ha

Re: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Igor Neyman
Title: RE: No Nulls? (was: Warehouse design: snowflake vs star schem Actually, you don't have to deal with "01/01/4000" date (at least on "select"), all you have to do in order find currently employed employees, is: where END_EMPLOYMENT sysdate asfor inserts, all you h

Re: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Ora NT DBA
[mailto:[EMAIL PROTECTED]] Sent: Monday, October 14, 2002 4:49PM To: Multiple recipients of list ORACLE-L Subject: RE: No Nulls? (was: Warehouse design: snowflake vs star schem Theproblem I see with NO NULLS is that artificial data must be created, where t

Re: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Marc Perkowitz
Title: RE: No Nulls? (was: Warehouse design: snowflake vs star schem This is true. But you still need to add logic to your application to suppress displaying the termination date when it is = "01/01/4000". Ican pretty well guarantee your users will not like seeing a &q

RE: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Jesse, Rich
Thinking about Matt's question, would it be proper to move the column to a EMP_TERMINATED table with an outer join on EMPNO? There wouldn’t be any NULLs... Rich Rich Jesse System/Database Administrator [EMAIL PROTECTED] Quad/Tech International, Sussex,

RE: No Nulls? (was: Warehouse design: snowflake vs star schem

2002-10-14 Thread Grabowy, Chris
other thoughts?? -Original Message-From: Fink, Dan [mailto:[EMAIL PROTECTED]] Sent: Monday, October 14, 2002 4:49 PMTo: Multiple recipients of list ORACLE-LSubject: RE: No Nulls? (was: Warehouse design: snowflake vs star schem The pro