Just discovered this project and am interested to see how it performs against laravel-mongodb
to do this we have lots of legacy laravel model builder methods that will need to have equivalents. I'm happy to write the overrides but need some pointers on getting started.
for example to use livewire-datatables a builder needs to be returned from an example query of:
So in this instance I need to create new methods for query(), when() , whereNull() , OrderBy() and paginate() which (I assume) will be via an extended Query/Builder.php (??) class
is this viable? is there a better way of handling this?
my start point was to override the MongolidModel with something like:
namespace App\Models\Overrides\Mongolid;
use MongolidLaravel\MongolidModel as BaseMongolidModel;
class MongolidModel extends BaseMongolidModel
{
public static function query() {
// return (new static())->getLocalMock();
return Container::make(Builder::class);
}
}
what would you suggest I return in the initial ->query() call? :-)
Hi,
Just discovered this project and am interested to see how it performs against laravel-mongodb
to do this we have lots of legacy laravel model builder methods that will need to have equivalents. I'm happy to write the overrides but need some pointers on getting started.
for example to use livewire-datatables a builder needs to be returned from an example query of:
then later in code, it calls
to return a LAP object.
So in this instance I need to create new methods for query(), when() , whereNull() , OrderBy() and paginate() which (I assume) will be via an extended Query/Builder.php (??) class
is this viable? is there a better way of handling this?
my start point was to override the MongolidModel with something like:
what would you suggest I return in the initial ->query() call? :-)
thanks in advance for any help.