View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002272 | Database Workbench v6 | General | public | 2025-02-26 10:09 | 2025-03-04 10:44 |
| Reporter | Martijn Tonies | Assigned To | Martijn Tonies | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | v6_next | ||||
| Summary | 0002272: Using a 'INPUT' for a subscript can fail when there's a comment in front of the statement | ||||
| Description | Using 'INPUT' for a subscript can fail when there's a comment in front of the statement | ||||
| Steps To Reproduce | 2) Whenever there is a comment (/* */ or --) before the INPUT keyword, it fails. Even a simple script like /* test */ INPUT 'test.sql'; fails with: Script Error: Dynamic SQL Error / SQL error code = 104 / Token unknown - line 2, column 1 INPUT A workaround I came up with is to insert a ";" before the INPUT, like /* test */ ;INPUT 'test.sql'; | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-02-26 10:09 | Martijn Tonies | New Issue | |
| 2025-03-04 10:43 | Martijn Tonies | Category | Firebird Module => General |
| 2025-03-04 10:43 | Martijn Tonies | Summary | Using 'INPUT' for a subscript can fail when there's a comment in front of the statement => Using a 'INPUT' for a subscript can fail when there's a comment in front of the statement |
| 2025-03-04 10:44 | Martijn Tonies | Assigned To | => Martijn Tonies |
| 2025-03-04 10:44 | Martijn Tonies | Status | new => resolved |
| 2025-03-04 10:44 | Martijn Tonies | Resolution | open => fixed |
| 2025-03-04 10:44 | Martijn Tonies | Fixed in Version | => v6_next |
