Read-Only model implementation

[mysticseagull]

I wrote a read-only mode trait for models to help with DX and causing fewer runtime errors when an a developer tries to insert data into a materialized view or other sources within a database, this trait also just allows disabling a model for writes in the case that you need it.

Originally I wrote this to stop some co-workers attempting to use the Eloquent ORM on materialized views without thinking causing them to run into SQL errors, this was my way of adding a fail-safe that is descriptive and quick, but also allowed me to add the idea of just disabling a model for any of it's write methods.

I have been debating on opening a PR for my implementation, wanted to hear some thoughts first on if this is useful.

<?php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;
use Illuminate\Database\Eloquent\ReadOnly;

class Season extends Model
{
    use ReadOnly;
}

[marius-ciclistu]

#53875

[mysticseagull]

#53875

I did see that yesterday, but my implementation is semi different, but also is not to have the same goal of unfreezing.

Granted, I can see the benefit of both.

Any feedback regardless would be more beneficial, I will publish the branch on my gh later today/tomorrow so more can be said.

Thanks 😁

[marius-ciclistu]

There there are 2 options. Frozen stdClass with autocomplete or model that will not see itself as dirty so it will not update but it will load relations from db for example or refresh it self.

Your solution is unclear in terms of implementation.

[michaelachrisco]

Just FYI here is a package that do what you wish for per model: https://github.com/michaelachrisco/ReadOnlyTraitLaravel

Its fairly popular and I keep it up to date. I discussed making it part of the laravel framework 9/10ish years ago(?) but I believe the consensus at the time was that they didnt want it in the main repo/setup. It has some niceties over the years that people have added to make it have more options.