Commenting constraints causes Internal Error
See original GitHub issueProblem: Adding a comment in the same style as the documentation to a constraints file leads to an Internal Error.
Expected behaviour: Commented constraints load or faulty comment syntax leads to Parsing/Syntax Error and/or commenting syntax for constraints is explained in documentation.
MWE:
- put the following in file and load. It works:
import webanno.custom.A_Event as Event;
Event {
a_Type = "ProductService" ->
b_Subtype="CancellationRecall" | b_Subtype="Launch" | b_Subtype="Trial" |
c_Participant.role="ProductService" (!) | c_Participant.role="Owner_ProductService" (!);
b_Subtype = "Trial" ->
c_Participant.role="Trialer" (!);
}
- Add a comment to the previous file. On upload, it redirects you to Internal Error page:
import webanno.custom.A_Event as Event;
Event {
// ProductService
a_Type = "ProductService" ->
b_Subtype="CancellationRecall" | b_Subtype="Launch" | b_Subtype="Trial" |
c_Participant.role="ProductService" (!) | c_Participant.role="Owner_ProductService" (!);
b_Subtype = "Trial" ->
c_Participant.role="Trialer" (!);
}
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
[YSQL] Internal error on creating a constraint that's ... - GitHub
When it's run in the order that the attached .zip) specifies, it reproducibly causes a server crash reported as shown above.
Read more >constraint error | OutSystems
The error message itself showing there is a foreign key constraint error, which means you are deleting a parent table where the child...
Read more >Handling Constraint Violations and Errors in SQL Server
The violation of any constraints leads to an error, and it is rare to see this handled well. Autocommit transaction mode. Let's create...
Read more >SQL Server error: introducing foreign key constraint on table ...
I have a On delete set null constraint set on both the foreign keys. SQL Server does not let me create the table...
Read more >13.1.20.5 FOREIGN KEY Constraints - MySQL :: Developer Zone
The CONSTRAINT symbol value, if defined, must be unique in the database. A duplicate symbol results in an error similar to: ERROR 1005...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have already done a documentation update locally and will commit it any moment.
Re-opening this issue because a proper error message should be displayed instead of an internal error page. Working on this.