Download the PHP package jpbourbon/redisgraph_php without Composer

On this page you can find all versions of the php package jpbourbon/redisgraph_php. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of jpbourbon/redisgraph_php

Informations about the package redisgraph_php

redisgraph_php

A client for RedisGraph aiming to track its development and implementation of OpenCypher. The goal of this library is providing a standard way of sending queries to the RedisGraph engine and encapsulate the results in a clean object.

Installation

Usage

There are 2 ways of using this library.

Connection

Client

RedisGraph

Queries

This library supports only raw queries. However, we encapsulate the query in a Cypher class that can be used for validation in future iterations. This class also provides tagging and runtime changing of graphs.

Running queries

Client

RedisGraph

Results

The response from the run method will return an instance of the Result class. This class consists of a structure that holds an array of query return keys, and array of RecordSets with *Records***, the Cypher object and the Statistics*** object.

Return keys

A Cypher query that contains a RETURN clause will always return a key:value pair, except when the query generates no returnable values. Consider the following Cypher query:

This returns the key f. To obtain an array with the returned keys, use the getKeys method:

Getting the RecordSet and Records

The *Result* and RecordSet*** objects provide methods to lookup their child classes.

Types of Records

The Records can be either Nodes, Relationships or Scalar values. Each of them has its own characteristics, reflected in the returned object. The distinct types of record can be easily identified using the getRecordType method:

Scalar

Scalar values are single values. Those can be either the result of an internal cypher function (such as SUM(), COUNT() etc) or the value from a node or relationship property.

To access the value you would first need to know the key, and use the getValue() method on the record:

However, as we often need to get a list of scalar values, there is a special method for that:

Nodes and Relationships

Nodes and Relationships share some common methods, since they can both hold properties, but have their specific ones. Common

Nodes

Relationship

Graphs

RedisGraph supports multiple graphs running alongside. This means the client must be flexible and support the different graphs. This client allows the definition of the graph in 3 different places: 1 - connection options; 2 - cypher object; 3 - chained method before running the query; The graph defined in the connection options is the default graph, and acts as a fallback in case no graph is defined anywhere else. The graph defined on the cypher query or the chained method is always considered secondary, and must be explicitely set to be used.

1 - Connection options

simply define the graph in the array:

2 - Cypher query

The graph is an optional argument when creating the Cypher object. If defined, overrides the default graph for the query execution.

3 - Chained method

This option is useful if the user intends to use the same Cypher object for different graphs, as it overrides both the default graph and the Cypher object graph:

Client
RedisGraph

Delete graphs

Graphs can be deleted with a simple delete method:

Client
RedisGraph

Explain queries

Both the RedisGraph and the Client classes feature an explain method that returns the query analysis:

Client

RedisGraph

TBC...

All versions of redisgraph_php with dependencies

PHP Build Version
Package Version
Requires php Version >=7.0
predis/predis Version ^1.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package jpbourbon/redisgraph_php contains the following files

Loading the files please wait ....