Do you let your database manage the way your application works, or do
you control the way it works?  Freedom.


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On
> Behalf Of K Kleinman Zajac
> Sent: Friday, December 07, 2001 12:24 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Duplicate Column Names = Foreign Key... UGH
> 
> >>  Then someone go so fed up
> with trying to think about it, they didn't care what the name was (I
> have a table that has 6 date columns, 2 of which are Date1, and
Date2).
> I want things done right this time around, and Rbase is forcing me
into
> bad practices. <<
> 
> This is totally unnecessary.
> 
> Why would you want FirstName, eg, to be different lengths anyway?
Either
> you need that space or you don't.  If there is really a difference
between
> the two, then the names should reflect that difference.  And I would
NOT
> use FirstNameA and FirstNameB.  I would use something that helps to
> describe the difference.
> 
> In the case of dates, it's really a no brainer.  A date type is a date
> type
> and they cannot be different lengths.  So even if you had, say
> "dateEntered" in six different tables, what's the big deal?  They are
all
> date type, so Rbase is happy, and there is no link between the tables,
so
> there should be no problems using it.  There is absolutely no reason
to
> give the column in each table a different name.
> 
> All of this has nothing to do with naming 6 date columns in one table
> date1, date2 etc.  That IS  bad practice, but is totally unnecessary.
> Surely you are not saying that you expect to have multiple columns in
ONE
> table with the same name?  So how does this get mixed into your
problem?
> ================================================
> 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

================================================
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

Reply via email to