Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Table aliasing are not supported in SQL update queries #6588

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

Table aliasing are not supported in SQL update queries #6588

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2018-04-21 09:12:11 +0200
From: Guillaume de GENTILE <<gentile_g>>
To: SQL devs <>
Version: 11.29.7 (Mar2018-SP1)
CC: @PedroTadim

Last updated: 2019-04-30 12:36:01 +0200

Comment 26397

Date: 2018-04-21 09:12:11 +0200
From: Guillaume de GENTILE <<gentile_g>>

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Build Identifier:

Table aliasing are supported in SQL select queries:
select a.* from table123 a --> OK

but not in SQL update queries!
update table123 a set a.COL1=0 --> ERROR
update table123 set COL1=0 --> OK

Reproducible: Always

Steps to Reproduce:

1.create a dummy table table123
2.update table using a table alias in SQL query
3.update table123 a set a.COL1=0 --> ERROR

Actual Results:

update table123 not successful
An error occurred when executing the SQL command:
update table123 a set COL1=0

ParseException:SQLparser:!42000!syntax error, unexpected IDENT, expecting SET in: "update table123 a" [SQL State=M0M10]
1 statement failed.

Execution time: 0s

Expected Results:

We need to be able to define table aliasing in SQL update queries.
update table123 a set a.COL1=0

Comment 26705

Date: 2018-11-29 17:57:37 +0100
From: @PedroTadim

I implemented this feature in merge-statements branch of MonetDB and it should be available in a future release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant