Skip to main content
Stack Apps

Return to Question

edited tags
Link
Kevin Montrose
Kevin Montrose
  • 18.7k
  • 6
  • 35
  • 62
added 148 characters in body
Source Link
Sky Sanders
Sky Sanders
  • 12.1k
  • 3
  • 32
  • 60

the suggested_buffer_size of user.about_me is currently 3000.

it is apparent that this is the server-side field length.

the problem is that the text is stored server-side in markdown but when served is expanded to html resulting in values that exceed 3000 characters.

when persisting, depending on the consumer, this can result in truncated data or truncation exceptions being thrown from the RDBMS.

it is my experience, gained by maintaining a complete user database, that a value of 4000 for suggested_buffer_size of 4000 is safe and more accurate.

also, I would suspect the same issue would apply to post body fields including comments, though I have not gathered metrics on those fields.

the suggested_buffer_size of user.about_me is currently 3000.

it is apparent that this is the server-side field length.

the problem is that the text is stored server-side in markdown but when served is expanded to html resulting in values that exceed 3000 characters.

when persisting, depending on the consumer, this can result in truncated data or truncation exceptions being thrown from the RDBMS.

it is my experience, gained by maintaining a complete user database, that a value of 4000 for suggested_buffer_size of 4000 is safe and more accurate.

the suggested_buffer_size of user.about_me is currently 3000.

it is apparent that this is the server-side field length.

the problem is that the text is stored server-side in markdown but when served is expanded to html resulting in values that exceed 3000 characters.

when persisting, depending on the consumer, this can result in truncated data or truncation exceptions being thrown from the RDBMS.

it is my experience, gained by maintaining a complete user database, that a value of 4000 for suggested_buffer_size of 4000 is safe and more accurate.

also, I would suspect the same issue would apply to post body fields including comments, though I have not gathered metrics on those fields.

Source Link
Sky Sanders
Sky Sanders
  • 12.1k
  • 3
  • 32
  • 60

user 'about_me' field suggested_buffer_size is too small

the suggested_buffer_size of user.about_me is currently 3000.

it is apparent that this is the server-side field length.

the problem is that the text is stored server-side in markdown but when served is expanded to html resulting in values that exceed 3000 characters.

when persisting, depending on the consumer, this can result in truncated data or truncation exceptions being thrown from the RDBMS.

it is my experience, gained by maintaining a complete user database, that a value of 4000 for suggested_buffer_size of 4000 is safe and more accurate.