Tore Bostrup wrote:
I'm sure you are aware that this is a non-normalized database design, and
that those tend to make designing queries more difficult and/or inefficient.
The LIKE operator should give you what you want, but you need to be careful:
(PHP string def:)
$sSQL = "SELECT
FROM
WHERE r
: 'Rich Hutchins'
Cc: [EMAIL PROTECTED]
Subject: RE: Perplexed by reverse SELECT statement.
Hi Rich,
I think that instead of a readBY column in your news table, you should
use what's called a lookup table. In this case, the lookup table would
store the primary key from the new
" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 04, 2003 8:42 PM
Subject: Perplexed by reverse SELECT statement.
> Man, this was a tough MySQL question to assign a Subject to. Hopefully the
> answer
> is easier.
>
> I have a table called news which con
Hi Rich,
I think that instead of a readBY column in your news table, you should
use what's called a lookup table. In this case, the lookup table would
store the primary key from the news table and the primary key from the
user table. Your table structure might look something like this:
user
-
Man, this was a tough MySQL question to assign a Subject to. Hopefully the
answer
is easier.
I have a table called news which contains a column called readBy. The read
by column is of type TEXT and it contains a CSV list of IDs of users who
have read a certain news item. For example, if my user ID
