Hi Miquel:
On Friday, August 24, 2012 2:01:02 PM UTC+2, Miquel Torres wrote:
yes, changing models.Report.summary length to 128 would be enough.
Then add a South migration for it, then apply it to migrate your DB.
Thanks, will try that when I find the time.
I don't remember well, but I would not think so.
I assume that these things are not actually checked and enforced consistently.
For instance, I can delete the reports in the admin pannel, and then they are correctly generated without complaining about the length.
Examples are:
SMarkSlopstone (1 cores, benchmarking.image ReBenchHarness 1 1 3000) +42.9%
SMarkSlopstone (2 cores, benchmarking.image ReBenchHarness 2 1 3000) +7.1%
LRSTMLoops.Send (1 cores, pharo-omni.image SMarkHarness 1 1 5000000) +17.4%
ATLoops.InstVarAccess (1 cores, pharo-omni.image SMarkHarness 1 1 900000) +32.5%
ATLoops.ArrayAccess (1 cores, pharo-omni.image SMarkHarness 1 1 2000000) +12.3%
ATLoops.ATInstVarAccess (1 cores, pharo-omni.image SMarkHarness 1 1 900000) +28.3%
SMarkSlopstone (2 cores, benchmarking.image ReBenchHarness 2 1 3000) +13.3%
GameSuite.Chameleons (2 cores, benchmarking.image ReBenchHarness 2 1 10000) +11.4%
GameSuite.Chameleons (1 cores, benchmarking.image ReBenchHarness 1 1 10000) +4.6%
And all these benchmark names are well beyond 30 characters.
To me it seems it is a minor issue anyway, the actual data seems to end up in the database, and only the report is not properly updated.
I will just work around (ignore) it for the moment.
Thanks
Stefan