I have a problem. At some point of time the cache of the following request ceases to be updated for the unknown reasons.

$newProducts = $product->catalogItem()
->whereNotNull('available')
->whereNull('preorder')
->orderBy('release_date', 'desc')
->limit($limitProductsOnTabs)
->get();

public function scopeCatalogItem($query)
{
return $query->select('products.id', 'image', 'name', 'rrp', 'wmr', 'activation_id', 'slug', 'has_discount', getNameCurr())->with('activation')->with('genres');
}

But the page of product is successfully cached. Why?

Hey,

Great package, thanks for releasing and maintaining this.

I currently have a problem that I just noticed, it was fine until a few hours ago.

The cache on my website doesn't get cleared when new "items" get added to the database. It doesn't happen with every model, just with a particular one.

It's quite odd to describe and it works just fine on my local env.

Here's a URL in case you want to see it: https://insegreto.com/it/fresh

In that page you'll find a list of posts. New posts are not visible until I manually clear the cache but you can see new comments right away.

I know the info is not much, but maybe you have already an idea of what's happening? Or maybe you can recommend a way to debug this?

--- EDIT More info. I'm using Envoyer to manage my deployments and after re-deploying (same code) everything is working as expected. I would expect though to have the same issue again in a few hours. Will keep posted.

--- EDIT #2 So.. after 6 hours, here we go again. Same issue. This time, re-deploying didn't fix the issue. I had to run php artisan lada-cache:flush.

So Lada creates a QueryBuilder here: https://github.com/spiritix/lada-cache/blob/master/src/Spiritix/LadaCache/Database/Connection.php#L31

But doesn't pass the fifth required argument, a model. Could this be an optional model? I guess telescope somehow uses this function and breaks because it tries to create a new instance of QueryBuilder without the Model.

I have a model (table) companies

id (index key), companyname, address, phone

I also have a model (table) categories

id (index key), category

this relation is many to many, companies may have many categories and one category may have many companies. For that reason I created a table companies_categories

id_company (index key), id_category (index key)

My question is if lada cache with the current logic will cache everything included the relation with row invalidation? As you see I have assigned both tables with primary key "id" but the relation table has no "id" and I am not sure how this will work.

Just wondering if there is a way to bypass the cache. For example, while doing a cron job and wanting direct query result, not a cached version. Or, do I simply need to flush the cache before doing the cron job?

Thanks

I've tried to use phpredis extension with lada-cache instead of Predis, but there is a problem where sadd parameters will not be properly passed to phpredis and on redis-cli monitor i see this

"SADD" "lada:tags:database:receptes:table:user:row:1" "Array" instead of "SADD" "lada:tags:database:receptes:table:user:row:1" "lada:90e60daab231709fb94aa8e729d54e51"

Not sure if you want to make old laravel versions incompatible since no changes in the actual package were made but I see that was done for the previous version so:

• Updated dependencies
• Updated factories
• Removed unsupported php from travis
• Migrated phpunit configuration
• Updated readme to reflect that phpredis is now default in laravel

I am getting old data after i updated some details. These are my files:

UserInfo.php

<?php

namespace App;

use Carbon\Carbon;
use Illuminate\Database\Eloquent\Model;

class UserInfo extends Model
{
    protected $guarded = [];

    use \Spiritix\LadaCache\Database\LadaCacheTrait;

}

User.php

<?php

namespace App;

use Illuminate\Foundation\Auth\User as Authenticatable;

class User extends Authenticatable
{
    use \Spiritix\LadaCache\Database\LadaCacheTrait;

    protected $guarded = [];

    protected $with = ['user_info'];

    public function user_info()
    {
        return $this->hasOne(UserInfo::class);
    }
}

$user = User::find(1);
echo $user->user_info->first_name // outputs 'test1';

then i tried to update his first_name like this:

UserService.php

$user_info = $user->user_info()->updateOrCreate(['user_id' => 1], [
	'first_name' => 'test2'
]);

then it results in this:

$user = User::find(1);
echo $user->user_info->first_name // outputs 'test1';

what is the issue here?

Of course this is not very pretty code, but what do you think of the idea?

It can be used like this: Article::cacheExpire(300)->where('publish_at', '<', \DB::raw('now()'))->limit(10)->get(); After 5 minutes (300 seconds) it will fetch from db again

Not working at the moment.

It would result in all models getting cached but not invalidated properly. This is because the class who writes values in the cache doesn't know which models are extending the cache model.

Also I am not sure what would happen if you join a model that is cached from a model which is not cached.

I am using default setup of spatie / laravel-permission package and lada-cache packages. Everything works well except user<->roles relation.

class User extends Authenticatable { use HasRoles; use LadaCacheTrait;

// ...

}

If i try to make request with 'roles' relation i'm getting an exception.

\App\User::whereHas('roles')->get();

TypeError Argument 1 passed to Spiritix\LadaCache\Reflector::getTablesFromWhere() must be an instance of Spiritix\LadaCache\Database\QueryBuilder, instance of Illuminate\Database\Query\Builder given, called in /home/belgiets/projects/laravel7/vendor/spiritix/lada-cache/src/Spiritix/LadaCache/Reflector.php on line 145

Reproduced on clear installation of:

• "laravel/framework": "^7.24"
• "spatie/laravel-permission": "^3.16"
• "spiritix/lada-cache": "^5.0"

When using tables with aliases IE: SELECT * FROM users AS user lada-cache returns the table as users AS user; The table name should actually be modified to use the real database table so that the tags are correctly wrote and cleared. I've recently started having issues with specific queries and noticed this bug.

I have fixed it locally by adding a preg_replace. Here are my changes in the Reflector class:

    /**
     * Returns all affected tables, including joined ones.
     *
     * @return array
     */
    public function getTables()
    {
        // Get main table
        $tables = [];
        if (is_string($this->queryBuilder->from)) {
            $tables[] = trim(preg_replace('#[\s]+(AS[\s]+)[\w\.]+#i', '', $this->queryBuilder->from));
        }

        // Add possible join tables
        $joins = $this->queryBuilder->joins ?: [];
        foreach ($joins as $join) {
            if (!in_array($join->table, $tables) && is_string($join->table)) {
                $tables[] = trim(preg_replace('#[\s]+(AS[\s]+)[\w\.]+#i', '', $join->table));
            }
        }

        $this->getTablesFromWhere($this->queryBuilder, $tables);

        return $tables;
    }

    /**
     * Get Table Names From Where Exists, Not Exists (whereHas/whereDoesnthave builder syntax)
     *
     * @param QueryBuilder $queryBuilder
     */
    private function getTablesFromWhere(QueryBuilder $queryBuilder, &$tables) {
        if (!isset($queryBuilder->wheres)) {
            return;
        }
        $wheres = $queryBuilder->wheres ?: [];
        foreach ($wheres as $where) {
            if ($where['type'] == 'Exists' || $where['type'] == 'NotExists') {
                $table = trim(preg_replace('#[\s]+(AS[\s]+)[\w\.]+#i', '', $where['query']->from));
                if (!in_array($table, $tables) && is_string($table)) {
                    $tables[] = $table;
                }

                // Add possible join tables
                $joins = $where['query']->joins ?: [];
                foreach ($joins as $join) {

                    if (!in_array($join->table, $tables) && is_string($join->table)) {
                        $tables[] = trim(preg_replace('#[\s]+(AS[\s]+)[\w\.]+#i', '', $join->table));
                    }
                }
            }
            if (isset($where['query'])) {
                $this->getTablesFromWhere($where['query'], $tables);
            }
        }
    }

    /**
     * Returns all affected rows as a multidimensional array, split up by table.
     *
     * @return array
     */
    public function getRows()
    {
        $rows = [];
        $wheres = $this->queryBuilder->wheres ?: [];

        foreach ($wheres as $where) {

            // Skip unsupported clauses
            if (!isset($where['column'])) {
                continue;
            }

            // If it doesn't contain the table name assume it's the "FROM" table
            if (strpos($where['column'], '.') === false) {
                $where['column'] = implode('.', [trim(preg_replace('#[\s]+(AS[\s]+)[\w\.]+#i', '', $this->queryBuilder->from)), $where['column']]);
            }

            list($table, $column) = $this->splitTableAndColumn($where['column']);

            // Make sure that the where clause applies for the primary key column
            if ($column !== $this->queryBuilder->model->getKeyName()) {
                continue;
            }

            // Initialize a set for the current table
            if (!isset($rows[$table])) {
                $rows[$table] = [];
            }

            // Add the rows to the current table set
            if ($where['type'] === 'Basic') {
                if ($where['operator'] === '=' && is_numeric($where['value'])) {
                    $rows[$table][] = $where['value'];
                }
            }
            else if ($where['type'] === 'In') {
                $rows[$table] += $where['values'];
            }
        }

        return $rows;
    }

This is for the Laravel 5.x branch and may need to be tweaked for 6.x. I have not upgraded to 6 yet, so I'm not able to put a PR as of this moment.

After some comprehensive testing, I figured out, that since Laravel 6 there are some queries that bypass Lada Cache. This doesn't cause unexpected behavior but reduces the effect of the cache. If used with Debug Bar, the "Queries" tab must not show any queries after the second page load. All queries which are still shown bypass the cache.

lada-cache on Laravel 6 is giving me some problem and sometimes the queries are not invalidated and subsequent queries to the database return inconsistent data.

I would therefore like to understand if it is possible to disable lada-cache for certain queries to the database, here is an example:

MyModel::withoutLadaCache()->updateOrCreate(...);

What do you think?

Note that since Laravel 5.7

php artisan cache:clear will not clear the default REDIS connection that lada-cache is configured to use (and doesn't appear to have any way to change)

This means that currently lada-cache is using the 'database' configuration of REDIS in Laravel (called 'default') (for things like sessions) and not the 'cache' configuration (called 'cache') .

The only work around I can see at the moment, is to change the redis cache configuration in Laravel (/app/config/cache.php) to have it's connection set to the 'default' and not 'cache'.

This of course undoes the reason it was changed in the first place, doing php artisan cache:clear will also delete anything placed in the REDIS 'database' configuration (i.e. sessions and the like)

Hello

Running the command php artisan scout:import App\Model it results in a fatal error thrown by lada cache:

Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes) in /home/runcloud/webapps/laravel-vivicity/vendor/spiritix/lada-cache/src/Spiritix/LadaCache/Encoder.php on line 43