Task #12610 (closed)
Opened 10 years ago
Closed 9 years ago
Bug: revisit 255-character limit on node.conn column
| Reported by: | mtbcarroll | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | 5.1.0-m3 |
| Component: | ORM | Version: | 5.0.5 |
| Keywords: | n.a. | Cc: | omero-team@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by mtbcarroll)
https://www.openmicroscopy.org/qa2/qa/feedback/10311/ reports in ome.services.blitz.fire.Ring.addManager an exception preventing server startup,
org.springframework.dao.DataIntegrityViolationException: could not insert: [ome.model.meta.Node]; SQL [insert into node (conn, external_id, permissions, down, scale, up, uuid, version, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?)] org.postgresql.util.PSQLException: ERROR: value too long for type character varying(255)
solved by switching conn to TEXT. Perhaps this, and other fields we put a large limit on, should indeed simply be TEXT columns. Or, we need to look harder at what content goes into this conn column.
Change History (3)
comment:1 Changed 10 years ago by mtbcarroll
- Description modified (diff)
comment:2 Changed 10 years ago by jamoore
- Milestone changed from Unscheduled to 5.1.0-m3
comment:3 Changed 9 years ago by jamoore
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Work begun on https://github.com/openmicroscopy/openmicroscopy/pull/3216
Workaround is:
ALTER TABLE node ALTER COLUMN conn TYPE text;