Issue #6382 has been updated by Nigel Kersten.
Assuming we implemented this, can I get any comments about the implications for adding database support further down the track? e.g. are similar semantics available for Postgres, Oracle, etc? ---------------------------------------- Bug #6382: We permit silent truncation, and probably other data corruption, in MySQL databases https://projects.puppetlabs.com/issues/6382 Author: Daniel Pittman Status: Needs Decision Priority: Normal Assignee: Nigel Kersten Category: Doh! Target version: Affected Puppet version: Keywords: Branch: At the moment, and as seen in #6380, we permit MySQL to silently truncate long strings rather than raising an error. We should probably send the appropriate set of "don't be stupid" configuration commands to MySQL to have it fail rather than corrupt information, including string truncation, magical zeroing of invalid dates, and so on. This would turn these into explicit failures, generate bug reports, and end up with code that doesn't lose data. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
