Terminal output problem matcher #45
Comments
Danieleeee
changed the title
|
This is a warning. Do you get any additional info if you run same code with SQL Developer or Toad? |
|
I wasn't looking for more info, but the possibility of highlighting errors in other colors, such as red and yellow. A bit like with the Success message: |
|
We have a problem matcher like this? |
|
If I add a comma in the last procedure parameter, in Toad I have this (PLS-00103): in oradew this: |
|
Look this one: |
|
There is already a problem matcher implemented. If you compile your object-file correctly placed in Src folder the problems should be matched. The problems are also parsed if you run file as a script but in your case the sql*plus outputed only "Warning: Package created with compilation errors". Can you try adding |
|
I have this configuration: {
"compile.warnings": "NONE",
"compile.force": true,
"compile.stageFile": false,
"source.input": ["./Database/**/*.sql","./Database/**/**/*.sql","./Database/**/**/**/*.sql","./Database/**/**/**/**/*.sql"],
"source.encoding": "win1250",
"source.pattern": {
"packageSpec": "./Database/{schema-name}/STOREDS/PKSPEC/{object-name}_h.sql",
"packageBody": "./Database/{schema-name}/STOREDS/PKBODY/{object-name}_b.sql",
"trigger": "./Database/{schema-name}/TRIGGERS/{object-name}.sql",
"typeSpec": "./Database/{schema-name}/TYPES/{object-name}.sql",
"typeBody": "./Database/{schema-name}/TYPE_BODIES/{object-name}.sql",
"view": "./Database/{schema-name}/VIEWS/{object-name}.sql",
"function": "./Database/{schema-name}/STOREDS/FUNC/{object-name}.sql",
"procedure": "./Database/{schema-name}/STOREDS/PROC/{object-name}.sql",
"table": "./Database/{schema-name}/TABS/{object-name}_tab.sql",
"synonym": "./Database/{schema-name}/SYNONYMS/{object-name}.sql",
"apex": "./Database/{schema-name}/APEX/{object-name}.sql"
},
"import.ease": true,
"import.getDdlFunction": "SIU.UTL_GENERATE_ORADEW.getDdl",
"package.input": ["./scripts/*.sql", "./Database/**/*.sql", "./scripts/**/*.sql"],
"package.exclude": ["./scripts/**/+(file|run|test)*.sql"],
"package.output": "./pubblicazione/{schema-name}.sql",
"package.encoding": "win1250",
"package.templating": false,
"test.input": ["./test/**/*.test.sql"],
"version.number": "0.0.1",
"version.description": "Gestione DB",
"version.releaseDate": "2020-01-01"
}and it shows me no errors when I compile the current file. Maybe the settings or the structure of the workspace is wrong |
|
Please send also the file content (you can ommit most of the body, leave enough to reproduce the error) and the file path. |
|
Is it possible that since my main folder is called "Database" and not "src", there could be problems? |
|
Yes, that could be a problem. it should be configurable in theory, but I never tested changing src folder. I will try to reproduce... You tried executing "compile current file", right? |
|
yes |
|
And what do you get as an error? |
|
no error |
|
Please post a print screen of terminal. |
|
|
|
"Database" instead of "src" shouldn't be a problem. Is it possible that you have a "strange" non latin char in your project name or something similar? (blurred text) |
|
Probably not related to your problem but: |
|
I have updated the configuration. |
|
Returning to the issue of errors with sqlplus, is it not possible to highlight the errors even in that situation? |
|
I cannot reproduce this issue, it seems to work for me. Do you still have this problem, @Danieleeee ? |
|
Yes. |
|
I use this button: |
|
If I add |
|
Yes, start fresh with a simpler project path (no blank spaces in project name, etc.) and default workspace configuration. |
|
Hi, I continue this report because the problem seems to me connected. this is an example: Even putting the "show err" command at the end of the script, the final output is "No errors" |
|
can you make problem matcher multilingual? when I have errors in Italian it writes ERRORE and not ERROR |
Hi,
is it possible to customize the terminal output when I run some package or script? Errors and warnings risk not being detected:
problem matcher?
I'm using Run Current File as Script (F5)
Thanks
The text was updated successfully, but these errors were encountered: