Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Index name "oc_reader_preferences"."reader_preferences_file_id_index" is too long. #18

Open
bohica70 opened this issue Sep 16, 2020 · 12 comments
Open

Index name "oc_reader_preferences"."reader_preferences_file_id_index" is too long. #18

bohica70 opened this issue Sep 16, 2020 · 12 comments
Labels
bug Something isn't working

Comments

@bohica70
Copy link

I tried to manually install the app, but when I click "enable" I receive the following error:

Index name "oc_reader_preferences"."reader_preferences_file_id_index" is too long.
@TheNomad11
Copy link

Still the same issue after today's update. But only on my NC 20 installation (and Ubuntu 20) , I did not see this error when updating on NC 19 (and Ubuntu 16.04) today

@TheNomad11 TheNomad11 mentioned this issue Oct 19, 2020
Closed
@e-alfred
Copy link
Owner

Which database type do you use?

@TheNomad11
Copy link

Postgresql - using the official VM, but I realised the app did install actually. After the error message it looked like it did not install, the button "download and enable" was still displayed. Now suddenly everything is fine even though I did not do anything

@bohica70
Copy link
Author

bohica70 commented Oct 19, 2020 via email

@TheNomad11
Copy link

TheNomad11 commented Oct 19, 2020 •
edited
Loading

I am using the official VM also, but still receive the error:
…

Oh sorry, I mixed it up with the music app that also got broken during the NC 20 update. The music app got fixed and is working now, but this app here is not working and I also still get this error message. Sorry!

@Cryx73
Copy link

Cryx73 commented Oct 20, 2020

Same on NC 20, Ubuntu V-Server with MariaDB, new installed Nextcloud, so first installation try of the reader.
No problems on NC19 on a hosted Webspace, app was only updating there.

This was referenced Oct 31, 2020
Closed
Closed
@e-alfred
Copy link
Owner

Can anybody of you try the new release here if the issue is fixed now?

https://github.com/e-alfred/epubreader/releases/tag/1.4.4

@ronsens
Copy link

ronsens commented Oct 31, 2020

Yes, it is! Tested with Nextcloud 20.0.1.

@e-alfred e-alfred added the bug Something isn't working label Nov 1, 2020
@infidelus
Copy link

Bingo. Working 👍

@StephenCYang
Copy link

Release 1.4.5 Works with NextcloudPi version 19.0.4.2!

Thank you!

@TheNomad11
Copy link

Working perfectly! Am also excited about how well it works on mobile!

aszlig added a commit to aszlig/avonc that referenced this issue Nov 4, 2020
@aszlig
tests/upgrade: Re-add "epubreader" to tested apps
834ac14 
When updating Nextcloud apps in 989a136,
I actually forgot about the assertion on epubreader 1.4.3, which was
exactly there so that we re-add epubreader to our tests.

I haven't run the full test yet, but according to some comment[1] in a
related issue, the issue has been fixed.

This fixes evaluation of our upgrade test.

[1]: e-alfred/epubreader#18 (comment)

Signed-off-by: aszlig <aszlig@nix.build>
@aszlig
Copy link

aszlig commented Nov 5, 2020

@e-alfred: Confirmed also in my automated tests, here's the log: https://headcounter.org/hydra/log/pzn7ja0w24dxx33cg2474z455pn5by4z-vm-test-run-nextcloud-upgrade.drv

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@aszlig @e-alfred @ronsens @TheNomad11 @StephenCYang @infidelus @bohica70 @Cryx73