Normalize oc_properties

[DeepDiver1975]

We waste rather much data space in oc_properties - normalization could help

here is an example of a instance with 20+k users

+---------------------------------------------------+----------+
| propertyname                                      | count(*) |
+---------------------------------------------------+----------+
| {DAV:}srt_modifiedtime                            |      477 |
| {http://apache.org/dav/props/}executable          |   240997 |
| {http://example.com/neon/litmus/}high-unicode     |        2 |
| {http://example.com/neon/litmus/}prop5            |        3 |
| {http://example.com/neon/litmus/}prop6            |        3 |
| {http://example.com/neon/litmus/}prop7            |        3 |
| {http://example.com/neon/litmus/}prop8            |        3 |
| {http://example.com/neon/litmus/}prop9            |        3 |
| {http://example.com/neon/litmus/}valnspace        |        2 |
| {http://www.southrivertech.com/}srt_creationtime  |   763561 |
| {http://www.southrivertech.com/}srt_modifiedtime  |   816907 |
| {http://www.southrivertech.com/}srt_proptimestamp |   816908 |
| {urn:schemas-microsoft-com:}Win32CreationTime     |   241259 |
| {urn:schemas-microsoft-com:}Win32FileAttributes   |   246384 |
| {urn:schemas-microsoft-com:}Win32LastAccessTime   |   242502 |
| {urn:schemas-microsoft-com:}Win32LastModifiedTime |   242532 |
| {}nonamespace                                     |        2 |
+---------------------------------------------------+----------+

The table has an overall size of close to 2GB of data!

Let's create a table which holds the propertyname and an id and use a fk to the oc_properties table

[PVince81]

cc @VicDeo

[PVince81]

nice to have but not high prio, moving to triage

[ownclouders]

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 7 days. Feel free to reopen this issue if you deem it appropriate.

(This is an automated comment from GitMate.io.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.