Type: Bug
- Join a table using temportal table syntax after in-line view join
- Join will be marked as syntax error. statement works on submission.
example:
create table tt_table
(
foo int not null primary key clustered
, bar varchar(50) not null
, validfrom datetime2 generated always as row start not null
, validto datetime2 generated always as row end not null
, period for system_time (validfrom, validto)
)
with (system_versioning = on);
select a.*, b.*, c.*
from tt_table for system_time all a
left outer join (
select b1.*
from tt_table b1
) b on b.foo = a.foo
left outer join tt_table for system_time all c on c.foo = a.foo
the join to c will be marked as an error incorrectly. if the join to 'b' is not in-line view, there are no intellisense issues.
error:
"owner": "mssql",
"severity": 8,
"message": "An expression of non-boolean type specified in a context where a condition is expected.",
"owner": "mssql",
"severity": 8,
"message": "Incorrect syntax near 'for'.",
owner": "mssql",
"severity": 8,
"message": "Incorrect syntax near 'all'. Expecting ID.",
Extension version: 1.15.0
VS Code version: Code 1.70.1 (6d9b74a70ca9c7733b29f0456fd8195364076dda, 2022-08-10T06:08:33.642Z)
OS version: Windows_NT x64 10.0.19042
Modes:
System Info
| Item |
Value |
| CPUs |
Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712) |
| GPU Status |
2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) |
undefined |
| Memory (System) |
31.92GB (21.96GB free) |
| Process Argv |
--crash-reporter-id b1acf4c8-3849-4a73-801a-58dc57c5ccec |
| Screen Reader |
no |
| VM |
0% |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411cf:30542925
vsaa593cf:30376535
pythonvs932:30410667
wslgetstarted:30449410
cppdebug:30492333
pylanb8912cf:30529770
vsclangdf:30486550
c4g48928:30535728
d7fjc500:30543455
dsvsc012:30540252
Type: Bug
example:
the join to c will be marked as an error incorrectly. if the join to 'b' is not in-line view, there are no intellisense issues.
error:
"owner": "mssql",
"severity": 8,
"message": "An expression of non-boolean type specified in a context where a condition is expected.",
"owner": "mssql",
"severity": 8,
"message": "Incorrect syntax near 'for'.",
owner": "mssql",
"severity": 8,
"message": "Incorrect syntax near 'all'. Expecting ID.",
Extension version: 1.15.0
VS Code version: Code 1.70.1 (6d9b74a70ca9c7733b29f0456fd8195364076dda, 2022-08-10T06:08:33.642Z)
OS version: Windows_NT x64 10.0.19042
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
A/B Experiments