# [Connections](http://facebook.github.io/relay/docs/graphql-connections.html)

- More powerful and flexible than simple lists.
- Support pagination (forward and back), with cursors.
- Fine-grained [mutation](http://facebook.github.io/relay/docs/graphql-mutations.html) support (eg. `RANGE_ADD`, `RANGE_DELETE`, `NODE_DELETE`, as described in [the guide](http://facebook.github.io/relay/docs/guides-mutations.html)).
- Requires a `first` or `last` argument in order to limit the size of the result set.
- Has an `edges` field that provides a place to locate per-edge, edge-specific data.
- A heavier-weight concept, requiring more work to define in the schema.

# Lists

- Simple and lightweight.
- No support for pagination (the entire list is always returned).
- No special mutations features for prepending, appending etc ([although it is a requested feature](https://github.com/facebook/relay/issues/444)).

# Which to use?

- Whenever you need pagination, you should use a connection.
- If you need fine-grained control over mutations, you may choose to use a connection, even if you don&#39;t need pagination.
- If you want all the items in a connection, you can use `first` with some large number.
- If you want to expose a short list with minimal effort, use a simple list.

For numerous time it has happened that our DevOps guys have created a Azure WebApp with incorrect URL. 

Which forced us the delete the resource group (as group contains web app, sql azure etc.) And re-create.


Is there a way to re-name /update the Web App URL via powershell Azure API or some hidden azure portal feature?

How to rename the Azure WebApp URL

Just wondering if there is convenient networkx function that returns a list of edges connected to a given node (or nodes) (e.g. `my_node_name`) in a graph (e.g. `G`).

I can do it this way:

    edlist=[]
    for ed in G.edges():
         if &#39;my_node_name&#39; in ed:
                edlist.append(ed)

but expect there might be a better way?

Get all edges linked to a given node in a networkx graph

In Relay GraphQL, connections and lists are both array-like, but they have different features. When should I use each?

When should I use a Relay GraphQL connection and when a plain list?

<p>In Relay GraphQL, connections and lists are both array-like, but they have different features. When should I use each?</p>


I started out with the `relay-starter-kit` and also worked my way through the Relay and GraphQL documentation. But there are quite a few areas that are unexplained and mysterious.

Seriously I read a lot of documentations everywhere about all these things but couldn&#39;t find any satisfying explanations for the following questions:

What is this for? I put logging but it never even gets called at all:

&lt;!-- language: lang-js --&gt; 

    var {nodeInterface, nodeField} = nodeDefinitions(
      (globalId) =&gt; {
        var {type, id} = fromGlobalId(globalId);
        if (type === &#39;User&#39;) {
          return getUser(id);
        } else if (type === &#39;Widget&#39;) {
          return getWidget(id);
        } else {
          return null;
        }
      },
      (obj) =&gt; {
        if (obj instanceof User) {
          return userType;
        } else if (obj instanceof Widget) {
          return widgetType;
        } else {
          return null;
        }
      }
    );

And what is the actual effect of this:

&lt;!-- language: lang-js --&gt; 

    interfaces: [nodeInterface],

Maybe related to that, what does the `node` field here do:

&lt;!-- language: lang-js --&gt; 

    var queryType = new GraphQLObjectType({
      name: &#39;Query&#39;,
      fields: () =&gt; ({
        node: nodeField,
        // Add your own root fields here
        viewer: {
          type: userType,
          resolve: () =&gt; getViewer(),
        },
      }),
    });

And what is the magic around the `id` field? What is `globalIdField` for?

I have an `id` in my database and thought I could use it in my GraphQL objects:

Instead of:

&lt;!-- language: lang-js --&gt; 

    id: globalIdField(&#39;User&#39;),

I want to use my database id:

&lt;!-- language: lang-js --&gt; 

    id: {
      type: GraphQLID,
      description: &#39;The identifier&#39;
    },

But if I do that I get an error in the browser saying `RelayQueryWriter: Could not find a type name for record &#39;1&#39;`.

I can get rid of that error by adding `__typename` to my component containers Relay Query but that seems all wrong.

It would be great if you could give some deeper insides and a better explanation here and enhance the official documentation.

Thank you

In Relay, what role do the node interface and the global ID spec play?

Pardon the naive question, but I&#39;ve looked all over for the answer and all I&#39;ve found is either vague or makes no sense to me. Take this example from the GraphQL spec:

    query getZuckProfile($devicePicSize: Int) {
      user(id: 4) {
        id
        name
        profilePic(size: $devicePicSize)
      }
    }

What is the point of naming this query `getZuckProfile`? I&#39;ve seen something about GraphQL documents containing multiple operations. Does naming queries affect the returned data somehow? I&#39;d test this out myself, but I don&#39;t have a server and dataset I can easily play with to experiment. But it would be good if something in some document somewhere could clarify this--thus far all of the examples are super simple single queries, or are queries that are named but that don&#39;t explain why they are (other than &quot;here&#39;s a cool thing you can do.&quot;) What benefits do I get from naming queries that I don&#39;t have when I send a single, anonymous query per request?

Also, regarding mutations, I see in the spec:

    mutation setName {
      setName(name: &quot;Zuck&quot;) {
        newName
      }
    }

In this case, you&#39;re specifying `setName` twice. Why? I get that one of these is the field name of the mutation and is needed to match it to the back-end schema, but why not:

    mutation {
      setName(name: &quot;Zuck&quot;) {
    ...

What benefit do I get specifying the same name twice? I get that the first is likely arbitrary, but why isn&#39;t it noise? I have to be missing something obvious, but nothing I&#39;ve found thus far has cleared it up for me.

What is the point of naming queries and mutations in GraphQL?

Assume you have a GraphQL type and it includes many fields.
How to query all the fields without writing down a long query that includes the names of all the fields?
    
For example, If I have these fields :

     public function fields()
        {
            return [
                &#39;id&#39; =&gt; [
                    &#39;type&#39; =&gt; Type::nonNull(Type::string()),
                    &#39;description&#39; =&gt; &#39;The id of the user&#39;
                ],
                &#39;username&#39; =&gt; [
                    &#39;type&#39; =&gt; Type::string(),
                    &#39;description&#39; =&gt; &#39;The email of user&#39;
                ], 
                 &#39;count&#39; =&gt; [
                    &#39;type&#39; =&gt; Type::int(),
                    &#39;description&#39; =&gt; &#39;login count for the user&#39;
                ]
                
            ];
        }

To query all the fields usually the query is something like this: 

    FetchUsers{users(id:&quot;2&quot;){id,username,count}}
But I want a way to have the same results without writing all the fields, something like this:

    FetchUsers{users(id:&quot;2&quot;){*}}
    //or
    FetchUsers{users(id:&quot;2&quot;)}

Is there a way to do this in GraphQL ??

I&#39;m using *Folkloreatelier/laravel-graphql* library.

How to query all the GraphQL type fields without writing a long query?

Graphql is great and I&#39;ve started using it in my app. I have a page that displays summary information and I need graphql to return aggregate counts? Can this be done?

Can graphql return aggregate counts?

The [relay docs][1] contain this fragment:

    query RebelsRefetchQuery {
      node(id: &quot;RmFjdGlvbjox&quot;) {
        id
        ... on Faction {
          name
        }
      }
    }

What does this `... on Faction` on syntax mean?

  [1]: https://facebook.github.io/relay/docs/graphql-object-identification.html#content

Content Type	Original Author	Original Content on Stackoverflow
Question	Greg Hurrell	View Question on Stackoverflow
Solution 1 - Graphql	Greg Hurrell	View Answer on Stackoverflow

When should I use a Relay GraphQL connection and when a plain list?

Graphql Problem Overview

Graphql Solutions

Solution 1 - Graphql

Connections

Lists

Which to use?

Get all edges linked to a given node in a networkx graph

How to rename the Azure WebApp URL

Attributions