Change Details

The old application truncates string values that are stored in the `data` blob to a maximum of 2048 characters: https://github.com/wmde/fundraising/blob/master/inc/spende.class.php#L601-L609 The new application should probably do that too, even when I can't figure out at the moment where such long values would come from. Question is, where to do it: * In the FundraisingStore entity * In the `Donation` domain object * In all places that generate values for `data` * On the framework level - always truncate HTTP GET/POST parameters. I'd vote for the `FundraisingStore` entity, but I fist want to consult with the others.

The old application truncates string values that are stored in the `data` blob to a maximum of 2048 characters: https://github.com/wmde/fundraising/blob/master/inc/spende.class.php#L601-L609 The new application should probably do that too, even when I can't figure out at the moment where such long values would come from. Question is, where to do it: * In the FundraisingStore entity * In the `Donation` domain object * In all places that generate values for `data` * On the framework level - always truncate HTTP GET/POST parameters. I'd vote for the `FundraisingStore` entity, but I first want to consult with the others.

The old application truncates string values that are stored in the `data` blob to a maximum of 2048 characters: https://github.com/wmde/fundraising/blob/master/inc/spende.class.php#L601-L609 The new application should probably do that too, even when I can't figure out at the moment where such long values would come from. Question is, where to do it: * In the FundraisingStore entity * In the `Donation` domain object * In all places that generate values for `data` * On the framework level - always truncate HTTP GET/POST parameters. I'd vote for the `FundraisingStore` entity, but I first want to consult with the others.