Support from Acquia helps fund testing for Drupal Acquia logo

Comments

killes@www.drop.org’s picture

Priority: Critical » Normal

The patch should not be neccessary becuase the location field is pruned to contain 128 chars. But - at least for pgsql- it doesn#t hurt either.

adrian’s picture

here is an updated patch, which fixes the problem with too many unique restraints on locales_target.

adrian’s picture

FileSize
1.96 KB

err. here is the patch.

adrian’s picture

FileSize
2.64 KB

here is a corrected patch, it contained some cruft fromt he taxonomy patch i made earlier

Gábor Hojtsy’s picture

Version: 4.5.0-rc »

Killes, the 128 char check is improperly implemented (the length is checked before a new substring of unknown length is added), so that check needs to be fixed in the first place.

Gábor Hojtsy’s picture

Killes, the 128 char check is improperly implemented (the length is checked before a new substring of unknown length is added), so that check needs to be fixed in the first place.

killes@www.drop.org’s picture

Component: postgresql database » locale.module
Assigned: vertice@www.drop.org » killes@www.drop.org
FileSize
739 bytes

How about this?

Steven’s picture

The first patch was apparently applied to CVS already. But it seems that in the pgsql code, the temporary column "old_location" is not dropped?

Still, we should decide on this... either we:
- Remove the substring checking completely and change "location" to text in both pgsql and mysql.
or
- We go back to a 128-char location, change the db columns back, and implement killes' improved checker.

By the way killes, I think the strlen($comm) < 128 in the while() condition is unnecessary with your later check in place.

Steven’s picture

Status: Needs review » Fixed

I don't think there's going to be any more follow-ups on this. Committed.

Anonymous’s picture

Anonymous’s picture

Anonymous’s picture

Anonymous’s picture

Anonymous’s picture

Status: Fixed » Closed (fixed)