id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,drp_resources,i_links,o_links,remaining_time,sprint 9971,Bug: OMERO.tables string columns are silently truncated,spli,spli,"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. Also, the column width defaults to 1 if nothing/0 is specified at initialisation. 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. ",task,closed,major,OMERO-4.4.7,API,,fixed,,analysis@…,,,,0,Bugs Fixing