Dmitry Yemanov wrote Fri, 08 Sep 2017 11:03:02 +0300:
1) d
2) c
3) b
4) b
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
Dmitry Yemanov wrote Fri, 08 Sep 2017 11:03:02 +0300:
1) d
2) c
3) b
4) b
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
Dmitry Yemanov wrote Fri, 08 Sep 2017 11:03:02 +0300:
1) d
2) c
3) b
4) b
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
Dmitry,
> Opinions, please.
>
> My personal votes: 1d, 2c, 3a, 4b
For myself: 1d, 2c, 3a or 3b, 4b
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
Hi,
1a
2c
3b
4b
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel
Hi,
1aBecause it is the same asFROM LEFT JOIN (SELECT)
2a LATERAL is for context reference and cannot be missed
3b if it work already as lateral but is this the true? Or only for referenced
stored proc?
4b as it should be derived table
Regards,Karol Bieniaszewski
Oryginalna wiadomość
All,
The key point of this standard feature is to allow sub-queries to
reference priorly defined contexts (in joins).
While thinking about this, I have a few questions to raise here. The
standard defines LATERAL for derived tables only. This sounds logical
but there are some corner cases to