DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=JwMgxkv7+zBEuaZBaTip2TQmISxWePDQhyxOIQTEVwq7mlvxxWRV+QmGKQdwrWEQhz
	F6+uXgBNQKi0uyEH9E4q4+QWxQt9S1LQmuG8p82YsJAq9RzeKlWr4O8dHOpcVCcCeLXd
	KWg5axDr1tI7Dgj6oMmHD0GSiR+c5Xu9V8bko=
MIME-Version: 1.0
In-Reply-To: <533df7fa1001082026h53b5d897x2fc1fa2a6f7ff6df@mail.gmail.com>
References: <533df7fa1001082026h53b5d897x2fc1fa2a6f7ff6df@mail.gmail.com>
Date: Sat, 9 Jan 2010 18:07:28 +0900
Message-ID: <1d581afe1001090107j7ace3eedm197d12b50579be58@mail.gmail.com>
Subject: Re: how to do this query
From: Ian Barwick <barwick@gmail.com>
To: Wes James <comptekki@gmail.com>
Cc: pgsql-sql@postgresql.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2010/1/9 Wes James <comptekki@gmail.com>:
> I have two tables:
>
> students
> =C2=A0stu_name
> =C2=A0schols_selected
>
> scholarships
> =C2=A0schol_name
> =C2=A0short_name
>
> schols_selected is made up of scholarships the students have selected,
> the field content will look like schol1:schol2:schol3
>
> I need a select that does something like this
>
> select schol_name, short_name, stu_name, schols_selected
> from scholarships, students
> where short_name is in schols_selected
>
> I have tried:
>
> where short_name like '%' || schols_selected || '%'
>
> but i'm not sure how to include a field result in between like operators.

Theoretically this construction is correct, but as the LIKE pattern is
probably longer than the contents of the field you are operating on,
it won't work in the way you intend it to.

> how do I get a list of scholarships based one which student selected
> it where the selected result is a string of colon seperated options?

I'm not quite sure what you mean here, but in order to be able to
match scholarships selected to an individual student given your table
structure, you could try turning the fields round, e.g.

  WHERE schols_selected LIKE '%' || short_name || '%'

However this is a lousy way of doing things and will cause performance
problems with a non-trivial amount of data. (An additional table is
what would would help you here).

HTH

Ian Barwick