From: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
---|---|
To: | "me(at)alternize(dot)com> <me(at)alternize(dot)com" <me(at)alternize(dot)com> |
Cc: | "Michael Fuhr" <mike(at)fuhr(dot)org>, <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: help with query: advanced ORDER BY... |
Date: | 2006-01-15 03:36:17 |
Message-ID: | 9FAD6CD1-B940-43EB-8FFF-E6FF20DF037A@myrealbox.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Jan 15, 2006, at 11:15 , <me(at)alternize(dot)com> <me(at)alternize(dot)com> wrote:
> the movie schedules for theatres normally contains the information
> theater_id, screen_date, screen_time, screen_number, movie_name and
> should be outputed accordingly. it now happens to have some cinema
> multiplex owners who for some reasons do not want to publish the
> screen_number to the public - but the internal data we receive does
> contain that information.
Something you may consider doing is creating a view that masks the
screen_number in those cases, something like
create view schedule_public_view as
select theater_id
, screen_date
, screen_time
, case when no_screen_number then 0 else screen_number end as
screen_number
, movie_name
from schedules;
Michael Glaesemann
grzm myrealbox com
From | Date | Subject | |
---|---|---|---|
Next Message | me | 2006-01-15 10:53:03 | Re: help with query: advanced ORDER BY... |
Previous Message | me | 2006-01-15 02:15:18 | Re: help with query: advanced ORDER BY... |