Skip to content
This repository has been archived by the owner on Jan 27, 2021. It is now read-only.

Need to truncate messages when inserting into db #181

Open
GoogleCodeExporter opened this issue Mar 12, 2015 · 1 comment
Open

Need to truncate messages when inserting into db #181

GoogleCodeExporter opened this issue Mar 12, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Example error:

An error occurred saving a build outcome for project {0}.  The detailed error 
message is "PreparedStatementCallback; SQL [insert into builds (project_id, 
uuid, status, message_key,message_arg_0, message_arg_1, message_arg_2, 
message_arg_3, build_reason_key, build_reason_arg_0, build_reason_arg_1, 
build_reason_arg_2, build_reason_arg_3, start_date, completion_date, 
build_number, update_type,work_dir, revision, revision_label, 
last_good_build_number,tag_name, repository_url, status_changed, 
scheduled_build,requested_by, revision_unavailable, broken_by_user_id, 
claimed_date, work_dir_vcs_clean) values ((select id from project_names where 
name=?), ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 
?, ?, ?, (select id from users where username=?), ?, ?)]; Data truncation: Data 
too long for column 'message_arg_0' at row 1; nested exception is 
com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 
'message_arg_0' at row 1."

Original issue reported on code.google.com by [email protected] on 2 Feb 2011 at 3:32

@GoogleCodeExporter
Copy link
Author

This issue was updated by revision 26b5372d22.

Truncate build failure message and build reason arguments to max length allowed 
by database.

Original comment by [email protected] on 3 Feb 2011 at 4:59

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant