I (Julian Foad) wrote: > I noticed that a fresh 1.8.x (pre-release) WC has a different schema from a > WC > created by 1.7.8 and upgraded by 1.8.x. (I haven't tried different 1.7.x > versions.) The differences are: > > --- schema-1.7.8-upgraded-to-1.8-dev > +++ schema-1.8-dev > > - file_external TEXT, > + file_external INTEGER, > > -CREATE INDEX I_ACTUAL_PARENT ON ACTUAL_NODE ( > - wc_id, parent_relpath); > +CREATE UNIQUE INDEX I_ACTUAL_PARENT ON ACTUAL_NODE ( > + wc_id, parent_relpath, local_relpath); > > -CREATE INDEX I_NODES_PARENT ON NODES ( > - wc_id, parent_relpath, op_depth); > +CREATE UNIQUE INDEX I_NODES_PARENT ON NODES ( > + wc_id, parent_relpath, local_relpath, op_depth); > > > This looks like a 1.8 release blocker.
Before anyone points out that these schema differences may not in themselves cause wrong functionality, I think the very fact that 'upgrade' doesn't make the schema identical is a blocker issue in itself. I don't know, and haven't tried to find out, whether there is any functional brokenness here. If the upgrade missed making these changes, then we definitely need to review this part of the upgrade to ensure it isn't missing any data changes that should be made along with these schema changes. - Julian > Filed as issue #4358 > <http://subversion.tigris.org/issues/show_bug.cgi?id=4358>.
