|Subject:||Re: OT - SQL Help needed...
|Date:||Fri, 2 Dec 2016 08:57:58 -0500
|From:||Jim Moseley <firstname.lastname@example.org>
My sql is rusty, so I'll let Liz & Larry talk about that. My concern is
with your design.
It seems like your Alias table has columns other than just an alias key
pointing back to the Locality table, like Alias Post Code. This doesn't
seem correct - Locality should be the only place for those fields. If a
user wants to specify their own Alias Locality, have them add 2 rows, 1
to Locality and one to Alias.
This would then solve your 'where can I get the Post Code from' issue.
> If the user entered an alias locality and the locality match is on the
> alias table (IN clause), how can I pick up other fields, such as postal
> code which may be different to the main locality postal code, in the
> alias table and put them in the query result? I.e. how do I know which
> alias record was matched in the IN clause?