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

Support optional error string #59

Closed
neverchanje opened this issue Jul 18, 2022 · 5 comments
Closed

Support optional error string #59

neverchanje opened this issue Jul 18, 2022 · 5 comments

Comments

@neverchanje
Copy link

neverchanje commented Jul 18, 2022

statement error string::interval: context-dependent operators are not allowed in computed column\nHINT: STRING to INTERVAL casts depend on session IntervalStyle; use parse_interval\(string\) instead
CREATE TABLE invalid_table (
  invalid_col interval AS ('1 hour'::string::interval) STORED
)

Statement error is also a part of the testing. In some circumstances, we may expect the system to produce errors as expected.

@skyzh
Copy link
Member

skyzh commented Jul 18, 2022

We already have

query error pgcode 42601
select count(sum(v3)) from t

Does this work for you?

@neverchanje
Copy link
Author

Am I using the wrong version?

sqllogictest --version
sqllogictest 0.5.4

My sqllogictest encountered the following failure:

query error pgcode 22000
select -1.702823466e+308 -1.702823466e+308
sqllogictest -p 4566 -d dev -u root 'test.slt'
[FAILED]

failed to parse sqllogictest file

Caused by:
    ParseError { kind: InvalidSortMode("pgcode"), loc: Location { file: "test.slt", line: 1 } }

Error: some test case failed:
[
    "test.slt",
]

@skyzh
Copy link
Member

skyzh commented Jul 18, 2022

Oh, then it might not be well-supported. I'll take a look...

@xxchan
Copy link
Member

xxchan commented Aug 13, 2022

Currently we only have statement error support.

Duplicate with: #30

@xxchan
Copy link
Member

xxchan commented Aug 15, 2022

close as duplicate

@xxchan xxchan closed this as not planned Won't fix, can't repro, duplicate, stale Aug 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants