[Share 2.0] Update db structure to stay backwards compatible

This commit is contained in:
Roeland Jago Douma 2015-12-15 09:51:16 +01:00
parent 12b0e9e3bd
commit 6c77d1734e
2 changed files with 7 additions and 7 deletions

View file

@ -684,7 +684,8 @@
</field> </field>
<!-- Foreign Key users::uid --> <!-- Foreign Key users::uid -->
<!-- This is the initiator of the share --> <!-- This is the owner of the share
which does not have to be the initiator of the share -->
<field> <field>
<name>uid_owner</name> <name>uid_owner</name>
<type>text</type> <type>text</type>
@ -694,18 +695,17 @@
</field> </field>
<!-- Foreign Key users::uid --> <!-- Foreign Key users::uid -->
<!-- This is the owner of the file, this can be <!-- This is the initiator of the share -->
different from the initiator of the share.
The naming is subobtimal but prevents huge
migration steps -->
<field> <field>
<name>uid_fileowner</name> <name>uid_initiator</name>
<type>text</type> <type>text</type>
<default></default> <default></default>
<notnull>false</notnull> <notnull>false</notnull>
<length>64</length> <length>64</length>
</field> </field>
<!-- Foreign Key share::id or NULL --> <!-- Foreign Key share::id or NULL -->
<field> <field>
<name>parent</name> <name>parent</name>

View file

@ -25,7 +25,7 @@
// We only can count up. The 4. digit is only for the internal patchlevel to trigger DB upgrades // We only can count up. The 4. digit is only for the internal patchlevel to trigger DB upgrades
// between betas, final and RCs. This is _not_ the public version number. Reset minor/patchlevel // between betas, final and RCs. This is _not_ the public version number. Reset minor/patchlevel
// when updating major/minor version number. // when updating major/minor version number.
$OC_Version = array(9, 0, 0, 5); $OC_Version = array(9, 0, 0, 6);
// The human readable string // The human readable string
$OC_VersionString = '9.0 pre alpha'; $OC_VersionString = '9.0 pre alpha';