Using pluck() on Query Leads to Crash about single-table-inheritance

[grzegorz-rozycki]

Same issue here. Instead of modifying the package I've overridden the newFormBuilder method.

<?php

namespace App;

use Illuminate\Database\Eloquent\Model;
use Nanigans\SingleTableInheritance\Exceptions\SingleTableInheritanceException;
use Nanigans\SingleTableInheritance\SingleTableInheritanceTrait;

class MyEloquentModel extends Model
{
    use SingleTableInheritanceTrait {
        newFromBuilder as private traitNewFromBuilder;
    }
    
    // ...

    public function newFromBuilder($attributes = array(), $connection = null) {
        try {
            return $this->traitNewFromBuilder($attributes, $connection);
        } catch (SingleTableInheritanceException $e) {
            return parent::newFromBuilder($attributes, $connection);
        }
    }
}

[jonspalmer]

A failing test case in a pull request would be helpful to track this down.

[00madz]

I ran into a similar issue when combining with the sluggable library trait. I ended up changing line 191:

throw new SingleTableInheritanceException("Cannot construct newFromBuilder without a value for $typeField");

To be:

return parent::newFromBuilder($attributes);

I guess on the assumption if you are dealing with a subset of fields you are probably not using full objects and base functionality is fine? I'm sure of the implications of doing this though, there are probably consequences

[nilay]

I stuck with same issue and hoping next release will have the fix.

[jonspalmer]

Fixed.