On Wed, Oct 20, 2021 at 6:58 AM Tom Lane wrote:
> "David G. Johnston" writes:
> > On Tuesday, October 19, 2021, Michael Lewis wrote:
> >> On Tue, Oct 19, 2021 at 3:48 PM Mithran Kulasekaran <
> >> [email protected]> wrote:
> >>> create view template_view (id, name, description, is_
"David G. Johnston" writes:
> On Tuesday, October 19, 2021, Michael Lewis wrote:
>> On Tue, Oct 19, 2021 at 3:48 PM Mithran Kulasekaran <
>> [email protected]> wrote:
>>> create view template_view (id, name, description, is_staged) as
>>> select t.id,t.name, t.description, false as i
On Tuesday, October 19, 2021, Michael Lewis wrote:
> On Tue, Oct 19, 2021 at 3:48 PM Mithran Kulasekaran <
> [email protected]> wrote:
>
>> create view template_view (id, name, description, is_staged) as
>> select t.id,t.name, t.description, false as is_staged
>> from template t
>>
On Tue, Oct 19, 2021 at 3:48 PM Mithran Kulasekaran <
[email protected]> wrote:
> create view template_view (id, name, description, is_staged) as
> select t.id,t.name, t.description, false as is_staged
> from template t
> left join template_staging ts on t.name = ts.name and
I thought a union mashed together two queries. The where clause can appear
in both. But the execution plan will almost certainly run the first query
and the second query. It should throw an error if the types don't match or
the number of columns don't match.
There are so few use cases for unions t
On Tue, Oct 19, 2021 at 2:48 PM Mithran Kulasekaran <
[email protected]> wrote:
> i think the only problem is when we try to use both union and where/join
> the issue starts to happen
>
I'm unconvinced this is actually an issue based upon what is presented
here. All I'm seeing is two
