Social: Using sqlite is broken

[juliushaertl]

{"status":-1,"exception":"Doctrine\\DBAL\\Exception\\DriverException",
"message":"An exception occurred while executing
'SELECT \"sn\".\"id\", \"sn\".\"to\", \"sn\".\"to_array\", \"sn\".\"cc\", \"sn\".\"bcc\", \"sn\".\"content\", \"sn\".\"summary\", \"sn\".\"published\", \"sn\".\"published_time\", \"sn\".\"attributed_to\", \"sn\".\"in_reply_to\", \"sn\".\"source\", \"sn\".\"local\", \"sn\".\"instances\", \"sn\".\"creation\"
FROM \"oc_social_server_notes\" \"sn\"
RIGHT JOIN \"oc_social_server_follows\" \"f\"
ON (\"sn\".\"to\" = \"f\".\"follow_id\")
OR (\"sn\".\"to_array\"

LIKE (? || (\"f\".\"follow_id\" || ?))
ESCAPE '\\')
OR (\"sn\".\"cc\"
LIKE (:dcValue3 || (\"f\".\"follow_id\" || :dcValue4))
ESCAPE '\\')
OR (\"sn\".\"bcc\"
LIKE (:dcValue5 || (\"f\".\"follow_id\" || :dcValue6))
ESCAPE '\\')
WHERE (\"f\".\"actor_id\" = ?)
AND (\"sn\".\"published_time\" \u003C ?)

ORDER BY \"published_time\" desc
LIMIT 5' with params [\"%\\\"\", \"\\\"%\", \"https:\\\/\\\/local.dev.bitgrid.net\\\/index.php\\\/apps\\\/social\\\/@admin\", \"2018-11-26 13:14:01\"]:\n\n

SQLSTATE[HY000]: General error: 1
RIGHT and FULL OUTER JOINs are not currently supported"}

@daita General error: 1 RIGHT and FULL OUTER JOINs are not currently supported

[ArtificialOwl]

Hmm, can we just ignore sqlite ? I mean the social app will generate a lot of requests and maybe SQLite should not be used ?

[juliushaertl]

@daita We should really make it possible to have this running on sqlite. Performance wise a sqlite database is never optimal, but when trying to get contributors involved requiring to have a full database server setup is a real blocker.

[ArtificialOwl]

I know, this is why the issue is still open :)

[juliushaertl]

Ok, just wasn't sure if we have already talked about that and we have a contributor here who is trying to start working on it a bit, but has just a sqlite setup :wink:

[jancborchardt]

@daita would be awesome if this could be fixed, it’s also a blocker for me right now working more on it. :)

[juliushaertl]

Fixed with #143 :tada: