[BUG] JSQLParser 5.3 Encountered unexpected token K_DO "DO".

http://jsqlformatter.manticore-projects.com/jsqlformatter/demo.html?args=-c%20JYOwzgpgTgLgBKGB7OBjJIBmA6MBXABwIBsBPAfVExQApgATAGjnogENjKm4oIClY5emxgRmUJMQjl0rAJQAoSFNTw8eBuQDmEENBHSAbgBYacxgt4FsrDlwtXsVgTCEGHfJ5OmyICzBIAtmgYOM6wYDx8CgBWSKAhWNgCrFCRKBhR1gxwALxwSE58LlwKmehYxMCqLCggSDAAFqBaQA

insert into conf.supply_info (id, deal_id, report_date, role_code)
select uuid_generate_v4(),
rep.deal_id,
rep.report_date,
rep.role_code
from conf.reports rep
join conf.orders o on rep.id = o.report_id
on conflict do nothing;

Unexpected K_DO "DO"
Expected one of these: "ON", "RETURN", "RETURNING", "ST_SEMICOLON".

But there is correct syntax for PostgreSQL

Greetings.

Unfortunately I can confirm this. The 'ON CONFLICT" collides with the 'JOIN ... ON', adding brackets to the SELECT ... works around.

insert into conf.supply_info (id, deal_id, report_date, role_code)
(select uuid_generate_v4(),
rep.deal_id,
rep.report_date,
rep.role_code
from conf.reports rep
inner join conf.orders o on rep.id = o.report_id)
on conflict do nothing;

fix(parser): parse INSERT ON CONFLICT after a join's trailing ON

fix(parser): parse INSERT ON CONFLICT after a join's trailing ON (JSQ…

Navigation Menu

Repository navigation

[BUG] JSQLParser 5.3 Encountered unexpected token K_DO "DO". #2358

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[BUG] JSQLParser 5.3 Encountered unexpected token K_DO "DO". #2358

Description

Activity

manticore-projects commented on Jan 1, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions