Re: same or different data types for disparate columns. I just discussed this with someone I work with. He is unfamiliar with Rbase, and works heavily in DB2. I wanted his reaction to the idea.
His response was "I can't say that's a bad thing." I've also noticed, that he does not use the same names for data elements as a matter of design practice. My point only is that whether or not the database engine should force the issue, it's hard to really argue that this is objectively a really bad thing in th engine. Maybe unnecessary and annoying, but that's a different issue. ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
