Darcs revisions break postgres

[vlstill]

When migrating to PostgreSQL Darcs repositories stopped working, the reason is that darcs contexts are much longer then the table column for revision, which has at most 256 characters. I had to perform following modifications of the database:

ALTER TABLE sourcestamps ALTER COLUMN revision TYPE text;
ALTER TABLE changes ALTER COLUMN revision TYPE text;
DROP INDEX IF EXISTS "changes_revision";
CREATE INDEX "changes_revision" ON changes USING hash ( revision );

Could you please change initialization of the database so that this is not necessary? The index change is necessary as btree indices have upper limit on index value size. The error was on 0.9.0rc1 (which is not in you selection list).

[tardyp]

Hi vlstill

The problem is that USING hash is not available under sqlite which is used by a lot of our users, so this is not as simple as that.

I dont understand why darcs did worked for you before with sqlite, as I would expect sqlite is supposed to enforce the varchar length

what is the style of a darcs revision?

In the tests I can see those have this form, which is incoherent with what you say

'got_revision', 'Tue Aug 20 09:18:41 IST 2013 abc@…', 'Darcs')

[dustin]

I believe sqlite does not enforce column lengths.

[anonymous]

migrated to ​https://github.com/buildbot/buildbot/issues/3013