Download the PHP package linkorb/extractor without Composer
On this page you can find all versions of the php package linkorb/extractor. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download linkorb/extractor
More information about linkorb/extractor
Files in linkorb/extractor
Package extractor
Short Description Extractor: extracts contexts through query packs
License MIT
Homepage https://github.com/linkorb/extractor
FAQ
Example:
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 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.
Informations about the package extractor
Extractor
Extractor is a library that allows you to extract data from connections (databases, files, API's, etc) into a simple JSON array for further processing.
No programming is required, all you need to do is write extractor definitions.
Use-cases
- Extract data from applications you can't modify
- Reporting
- Collecting Context data (all records related to entity "X").
Extractor + Context = <3
Extractor works particularly well in tandem with github.com/linkorb/context
You can use the output of Extractor to load the data into a Context for further processing. This gives you the ability to specify advanced multi-directional relationships for flexible in-memory navigation.
Example: wordpress-post-extractor.yaml
Check the examples/wordpress-post-extractor.yaml definition file for a simple example.
This example requires one Input called postName.
Based on the input, it runs a set of commands.
Each command has a method. Different connections support different methods. The PdoConnection supports the query method, while an XyzApiConnection would support methods like request.
You can specify an SQL query that contains a set of placeholders.
The placeholders are passed as arguments into the command before it's executed. This allows you to pass arguments from the "inputs" table, or from a table that has been queried before.
In the wordpress example you'll see that the first command passes the postName from the initial inputs.
The second command passes in the postId that was retrieved during the first command.
This allows you to stack queries on top of each-other.
Output format
Extractor collects a set of tables, with rows per table. You can think of it as snapshot of a database.
The output is a simple array (which you can json_encode) that looks like this:
You'll see the "inputs" have is provided as a table containing a single row. The "posts" table contains one row, the one selected based on the input argument. And the comments table contains all rows matched by the postId.
Note that rows don't have a key, it's up to the code that uses these extracts to assign row ids or build indexes if needed.
A simple way would add useful IDs to the comment table based on the comment_ID of each row would be:
License
MIT (see LICENSE.md)
Brought to you by the LinkORB Engineering team
Check out our other projects at linkorb.com/engineering.
Btw, we're hiring!
