[TYPO3-core] RFC: #10201: Duplicate cHash Values

[Dan Osipov]

Yes, char field would be more efficient. But that's a change in realURL.

In my opinion, longer cHash will drive adoption of realURL, since it 
removes the cHash from the URL (among other features). So if someone 
thinks it s a problem they have an easy solution.

Thanks a lot, Dmitry!

Dan Osipov
Calkins Media
http://danosipov.com/blog/

Dmitry Dulepov wrote:
> Hi!
> 
> Dan Osipov wrote:
>> Can this be included in alpha3?
> 
> One tiny thing in this patch can be optimized. The database field for cHash should be char(32), not varchar(32). It is always 32 bytes, so char(32) makes sense there.
> 
> RealURL is almost ready for this TYPO3 change.
> 
> One thing that bothers me is that cHash will be visually much longer in the URL. Otherwise I see no disadvantages.
> 
> What do others think? Should we have proper md5s in cHash?
>