Download the PHP package vkr/view-materializer-bundle without Composer
On this page you can find all versions of the php package vkr/view-materializer-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 view-materializer-bundle
About
A materialized view is a table that does not contain any original data - any of its data comes from a SELECT query on some other tables. Unlike simple views, materialized views are stored on disk as simple tables. Any query on a materialized view works much faster than on a simple view, however, materialized views need to be regularly updated to reflect changes in their underlying tables. Some DB engines have default support for view materialization, but MySQL does not.
This is a simple bundle that was created to emulate materialized views in MySQL. It depends on Doctrine and is available both as stand-alone service and console command that can be launched via Cron. It also depends on VKRCustomLoggerBundle.
Currently, this bundle does not support multiple DB connections and will always use default connection.
Installation
Besides enabling the bundle in your , you must configure it and create a log file.
The log file needs to be placed into , it should have extension and, of course, it should be open for writing.
To configure the bundle, create key in your or in any other included configuration file. Under this key, you need two keys: contains your log file name without path and extension. key contains the main bulk of configuration, namely - a dictionary with keys that correspond to materialized view names and values that are SELECT queries that create these views.
Example in YAML:
Usage
There are two ways to use this bundle - from a controller or from console.
If you use it from the console, enter . If your configuration is as in the example above, Doctrine will attempt to make these queries:
If you are using Symfony 3, swap for .
If there are any errors, they will be output to your log file.
From the controller, you need to call:
If there are any errors, will be returned and the errors logged to the file.
API
void ViewMaterializer::__construct(Doctrine\ORM\EntityManager $em, VKR\CustomLoggerBundle\Services\CustomLogger $logger, string[] $definitions, string $logFile)
bool ViewMaterializer::materializeViews()
In case of an error while executing a query, execution will be immediately stopped and false returned. Otherwise, returns true.
All versions of view-materializer-bundle with dependencies
symfony/symfony Version ~2.8|~3.0
doctrine/orm Version >=2.2.3
doctrine/doctrine-bundle Version ~1.4
vkr/custom-logger-bundle Version ~1.2