You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This problem is related to the DB table offlines where the binaryBitbucket field was a varchar(40) and was generating an error that the field was too small for data of some types being put into it. However, extending the fields size to varchar(80) while is solved the SQL error, did not correct the problem of data transfer. I suspect there is a problem with how the attached item is getting encoded and decoded from that field.
Similar problem with Group Notice attachments and its osgroupnotice.BinaryBitbucket field posted in a separate issue.
The text was updated successfully, but these errors were encountered:
This problem is related to the DB table
offlines
where the binaryBitbucket field was a varchar(40) and was generating an error that the field was too small for data of some types being put into it. However, extending the fields size to varchar(80) while is solved the SQL error, did not correct the problem of data transfer. I suspect there is a problem with how the attached item is getting encoded and decoded from that field.Similar problem with Group Notice attachments and its osgroupnotice.BinaryBitbucket field posted in a separate issue.
The text was updated successfully, but these errors were encountered: