|
 |
"clipka" <ano### [at] anonymous org> wrote in message
news:4ae9b09e$1@news.povray.org...
> Captain Jack schrieb:
>
>> SELECT C.Name, U.UserName
>> FROM tblClients AS C
>> OUTER JOIN tblUsers AS U ON U.UserId = C.LastEditUserID
>>
>> In that case, the column LastEditUserID is zero (another way of logically
>> saying Null, I s'pose) when the client row is new and has never been
>> edited. I do that so that in that query I always get the client data,
>> with the user name being optional.
>
> In theory, you'd solve this by adding another entry to tblUsers with
> default values to use for new clients.
Which hikes up my filtering costs later... When I show a list of users to
select for, say, a report, I have to filter out the "special cases" that
aren't actually users. I'm effectively making the User table track two
different kinds of data, and I have to take that into account in all my
future use of the table. Probably by adding a column to the table to flag
how it's used. Then I have extra documentation tasks, more maintenance
problems...
Okay, now I'm whining. Sorry about that... I just got out of a three hour
design meeting where we ran out of coffee, and my head hurts. :D
Post a reply to this message
|
|
