-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Schema mismatch for _Session.expiresAt #220
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.
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
Comments
This symptom should be fixed in the latest version, 2.0.6, but if you had run an older version, your _SCHEMA record for _Session may have been committed with "number" as the type for the "expiresAt" column. In that case, you will need to edit the entry in your mongo database. If you need help with that, let us know. |
@gfosco But on the heroku server with the same mongo database uri it's working as expected. NOTE: I am using 2.0.6 on my local server just updated and on heroku I deployed the server by clicking on the deploy button on github repo of parse-server-example. |
You're right, I ran this: db.getCollection('_SCHEMA').update({_id: '_Session'}, {'$set': {expiresAt: 'date'}}) on a mongo shell and it appears to be working. |
Hi, I changed my schema in and I'm still having this issue. I am using MongoLabs for my db provider. Any idea why this would still be happening? |
If you've changed the schema, what is the error you're getting now? |
I'm getting the same error and I'm not really sure why that would be.
This is what my schema looks like when I log in to mongo labs and look at the _SCHEMA:_Session document:
|
You'll need to edit that entry and change the expiresAt entry from string to date. |
That did it for me. I thought it was the other way around. Thanks. |
…rse-server-2.2.12 Upgrade to parse server 2.2.12
The text was updated successfully, but these errors were encountered: