Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
12/10/12 15:37:25 (11 years ago)
- Author:
-
spli
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Status
changed from
new
to
accepted
- Property Cc analysis@… added
-
Property
Component
changed from
General
to
API
-
Property
Remaining Time
changed from
to
0.5
-
Property
Summary
changed from
OMERO.tables string columns are silently truncated
to
Bug: OMERO.tables string columns are silently truncated
-
Property
Priority
changed from
minor
to
major
-
Property
Milestone
changed from
to
OMERO-4.5
-
Property
Sprint
changed from
to
2012-12-18 (3)
-
Property
Type
changed from
bug
to
task
-
initial
|
v4
|
|
1 | 1 | String columns in OMERO.Tables have a width that is defined when the table is initialised. If a string longer than than this width is inserted it is silently truncated. |
| 2 | |
| 3 | Also, the column width defaults to 1 if nothing/0 is specified at initialisation. |
| 4 | |
| 5 | Fixes to either of these could be considered (undocumented) API changes. The first should be uncontroversial, the latter I consider a bug too: I think the main reason a user would omit the width is if they thought StringColumns could hold strings of any length, whereas the current implementation creates a column of width 1 and silently truncates added data. It's unclear whether #1716 was intended to work around only uninitialised columns, or to deliberately default to size 1. |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.12741 sec.)