Skip to content

data type (response) changing when migrating Parse server to New server #806

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

Closed
MuseerAnsari opened this issue Mar 3, 2016 · 4 comments
Closed

Comments

@MuseerAnsari
Copy link

Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

-[ ] You've met the prerequisites.

-[ ] You're running the latest version of Parse Server.

-[ ] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup

Steps to reproduce

Logs/Trace

@MuseerAnsari MuseerAnsari changed the title data type (response) id changing when migrating to parse server data type (response) changing when migrating to parse server Mar 3, 2016
@MuseerAnsari
Copy link
Author

Result (response) after query From old server (originally parse server)
Array (
Dictioanry1{},
Dictioanry2{},
Dictioanry3{},
.
.
.

)

And from new server after same Query

Array (
Dictionary{
Array(
Dictioanry1{},
Dictioanry2{},
Dictioanry3{},
.
.
.
)
},
)

@flovilmart
Copy link
Contributor

What version of parse-server are you running? What is your query?

@flovilmart
Copy link
Contributor

Duplicate from #803

@MuseerAnsari MuseerAnsari changed the title data type (response) changing when migrating to parse server data type (response) changing when migrating Parse server to New server Mar 3, 2016
@MuseerAnsari
Copy link
Author

i am using PARSE_VERSION @"1.12.0"
and my query is when i am fetching data from AWS server then its structure is diffrent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants