On Mon, 2005-05-02 at 10:49 -0500, Michael Parker wrote:
> On Mon, May 02, 2005 at 04:33:28PM +0100, Mike Grice wrote:
> >
> > Nope, but think of how it would scale. The design above is bad because
> > there is no unique data in there, so the table will get slow. A better
> > design would be thi
On Mon, May 02, 2005 at 04:33:28PM +0100, Mike Grice wrote:
>
> Nope, but think of how it would scale. The design above is bad because
> there is no unique data in there, so the table will get slow. A better
> design would be this:
>
Howdy,
SpamAssassin is an open source project that welcomes
On Mon, 2005-05-02 at 09:34 +0200, Arvinn L?kebakken wrote:
>
> Gerald V. Livingston II wrote:
>
> >OK, this is probably just an over-cautious MySQL question.
> >
> >All of the examples I look at for setting up per-user prefs using SQL show
> >creating a table that looks like:
> >
> >username pr
Gerald V. Livingston II wrote:
OK, this is probably just an over-cautious MySQL question.
All of the examples I look at for setting up per-user prefs using SQL show
creating a table that looks like:
username pref value
So, if I want to allow users to control 5 values I would have a table that
lo
Gerald V. Livingston II wrote:
OK, this is probably just an over-cautious MySQL question.
All of the examples I look at for setting up per-user prefs using SQL show
creating a table that looks like:
username pref value
So, if I want to allow users to control 5 values I would have a table that
loo
OK, this is probably just an over-cautious MySQL question.
All of the examples I look at for setting up per-user prefs using SQL show
creating a table that looks like:
username pref value
So, if I want to allow users to control 5 values I would have a table that
looks like thsi:
user1 pref1
