Skip to content

Column name restrictions enforced on sub-object keys #165

Closed
@sdf611097

Description

@sdf611097

I just migrate the db to mongolab.

I start the parse server example.

I try to query something with javascript sdk 1.7.0 on nodejs v4.2.4.

Below is my javascript code.

var Parse = require('parse/node').Parse;
Parse.initialize("myAppId", "jsKey");
Parse.serverURL = 'http://localhost:1337/parse'

var clz = Parse.Object.extend('myClass');
var query = new Parse.Query(clz);
query.find().then(function(list){
console.log(list.length);
},function(error){
console.log(error);
});

One of my original class(size 4) will get ParseError { code: 1, message: undefined }.

Others get all obj size (not original default limit 100)

I use original keys and with default parse api server endpoint.

It works, and get 4 and 100 as expected.

I found that query.limit default 100 is gone.
query.skip cannot exceed 10000 constraint is gone.
Could you also list all influence of the code?
(In this case, query with 100 results must add query.limit(100); )

Only contains 'hello' cloud code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:bugImpaired feature or lacking behavior that is likely assumed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions