Tell me about your experience with Pro*C.
For this hands-on SQL exercise, demonstrate the data-reporting aspect by writing a PostgreSQL query over the supplied Pro*C batch and error-log tables. Include eligible batches even when they have no matching errors.
batch_id, run_date, program_name, status, error_count, critical_error_count, rejected_rows.run_date ascending, then batch_id ascending.| Column | Type | Description |
|---|---|---|
| batch_idPK | INT | Identifier for the Pro*C batch execution |
| run_date | DATE | Date on which the batch ran |
| program_name | VARCHAR(100) | Name of the Pro*C executable |
| status | VARCHAR(20) | Execution status |
| Column | Type | Description |
|---|---|---|
| error_idPK | INT | Identifier for the logged error |
| batch_id | INT | Batch associated with the error |
| severity | VARCHAR(20) | Error severity |
| error_code | VARCHAR(30) | Application or database error code |
| rejected_rows | INT | Number of rows rejected by the error |