-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
SQLException: Unkown Column 'created' in 'where clause' #883
Comments
Never mind, I droppped all |
I actually noticed this problem myself just yesterday, although it has been introduced already two months ago in v1.2.1. The thing is, when I added the NC22 support in v1.2.1, the DB migration broke for such cases where the new version of Music is installed over previous version older than v1.0.0. And that older version doesn't actually need to be active at the moment of installation; it's enough for the problem to arise if any older versions have ever been installed on the same cloud instance. The problem affects Nextcloud but not ownCloud. I'll try to fix this for the next release of the Music app, although there probably is all the time less and less such setups where Music older than v1.0.0 is present. In the mean time, the easiest workaround is just the one described above: drop the |
Alright, thanks for letting me know - this might be helpful for some users! For me I was pretty sure I had no playlists et cetera created back when I was testing the app, so no loss of data by dropping the tables. (...and by the way, it works like a charm now - thank you so much for this very nice app!) |
When defining the DB schema for Nextcloud was moved to use the migrations mechanism in v1.2.1 (commit 6982d91), a problem was introduced: The migration worked only either on a clean database (no earlier versions of Music installed) or on v1.0.0 or newer. Installing over any v0.x.y got broken. This was because the auto-generated migration script Version010200Date20210513171803 newer altered the DB schema of existing tables; it just created tables which were missing. The not so well-working migration script has now been replaced with the hand-written Version010000Date20210903000000. This script checks separately that each needed column exists in the database and creates the missing ones. It also removes couple of obsolete columns (removed over the years) if those are still present in the database. This new script should be able to migrate the database from any version starting from v0.4.0 to the v1.0.0 level. Most of these versions have not been tested, though. refs owncloud#889 refs owncloud#883
The application update over any older Music (database) version should now work with Music v1.3.2. |
I am attempting to install the Music app 1.3.1 on a Nextcloud 21 and - during the installation - am faced with the exception shown below. I am not 100% sure I have never had the Music app installed, but if so that must have been years ago. I am adding this because the error looks a bit like there were some tables already present in my database? If this is the case I'd love to learn which tables to drop in order to be able to install this app (again?)
The text was updated successfully, but these errors were encountered: