great stuff thanks!

how are indexes handled? is it just on keys and foreign keys? for instance can I implement a geo-query?

e.g. posts near me

@monkeybonkey In general we manage indexes required to maintain performance of your queries. Additionally you will be able to enable specific indexes to enable extra functionality such as geo-queries. Geo datatypes is on our roadmap for December and we plan to enable the Algolia integration for full text search by the end of this month. Feel free to add your use case to the feature request list to help us prioritize the right features https://github.com/graphcool/feature-requests/projects/1

hi

i set up some relations between my models and since then i have error message about permission i'am using appolo-client

hey @dydycloud do you allow access to all fields? you can check that in the permissions page

i just re do that action and everuthing work but i have to do it twice

thank great reactivity there

you can select "Apply to whole model" to allow access to future fields automatically

first time i try manually but it failled, second time yes i use "Apply to whole model" .

you really doing a great job with that app you're like a firebase but for graphql : userfriendly and efficient

@schickling , @nilan having problems querying my endpoint - do I need to send any headers? react app, cURLing, or using postman.app always gives cloudfront errors -

The request could not be satisfied.

😞

Hey @herrhelms! I'll reach out to you via PM 🙂

Hi all! I’m getting error

Code 3008: InsufficientPermissions

, though i am logged in in client, so i tried removing all field permissions. but i keep getting this error when i from my app requests

posts(filter: {title: $title}) {
        id
        title
        tags {
          id
          name
        }
      }

Where tags is a many to many relationship with post, but user too. The same query works fine in playground. Any ideas ?

The relation is added today, so after you added the permissions section to console. i don’t know if it’s connected

It happens with any new relation i try to create. It can be one to many or many to many. The relations i created 2 weeks ago still works very well and doesn’t have permission issues

It had something to do with Permissions, but i fixed it by added no permissions to the whole model. Might be a bug, should i make a github issue?

@emilrmoeller what are the permissions on the

tag

Model? Can you do allTags with eg. first: 5?

Seems like the permissions on the Tag Model are not Set properly

Currently we shouldnt have relations effecting the permissions, if yes it's definitely a bug

Hey @tim2 all permissions where for everyone, the issue was i think that the permission model for the

Post

model was created before the

Tags

was a field on

Post

. So it wasn’t permitted, because it wasn’t available when the permission model was created

Ok, that makes sense, then it's probably a bug on our side

Would be nice if you could create an issue :)

But relation fields doesn’t seem to be available in the permission tool, but adding

apply to the whole model

seems to work

Ill do that 🙂

Oh that's not how it should be, but good that you could for now find a work around

Thanks!

@tim2 hehe nope, i would like it to be as a field hehe, but it’s good for now until a better solution comes up 🙂

@emilrmoeller ah I see, we will fix it asap :)