View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001105 | savapage-core | [All Projects] General | public | 2020-01-08 20:47 | 2020-02-25 09:34 |
| Reporter | rijkr | Assigned To | rijkr | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.1.0 | ||||
| Target Version | 1.2.0 | Fixed in Version | 1.2.0 | ||
| Summary | 0001105: Avoid empty string on not-null database column | ||||
| Description | IST: Oracle DB interprets an empty zero-length string as NULL value. When set on a JPA "nullable = false" database column, this causes "ERROR - ORA-01400: cannot insert NULL". SOLL-1: Do not set empty string on JPA "nullable = false" database column. SOLL-2: Beware that Oracle DB stores empty string on "nullable = true" column as NULL value. https://schneide.blog/2010/07/12/an-oracle-story-null-empty-or-what/ | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-01-08 20:47 | rijkr | New Issue | |
| 2020-01-08 20:47 | rijkr | Status | new => assigned |
| 2020-01-08 20:47 | rijkr | Assigned To | => rijkr |
| 2020-01-09 12:39 | rijkr | Relationship added | related to 0001109 |
| 2020-01-14 12:41 | rijkr | Status | assigned => resolved |
| 2020-01-14 12:41 | rijkr | Resolution | open => fixed |
| 2020-01-14 12:41 | rijkr | Fixed in Version | => 1.2.0 |
| 2020-02-25 09:34 | rijkr | Description Updated | View Revisions |
