Cristian Llanos

Sounds really cool!

A different approach is needed to consider a broader range of use cases. For instance, relationships methods could be moved to the child classes, but it could cause other problems...

It's been designed that way in order to keep track of cross schema relations. The way it works is when you specify a schema, it will only override files belonging...

The algorithm can be improved to lazy load schemas instead of eager loading them. This new approach would potentially solve this problem. Pull requests are welcomed.

I think you might be able to fix it by overriding the $casts attribute (if you've enabled [base_files](https://github.com/reliese/laravel#1-keeping-model-changes)). Pull requests are always welcomed and encouraged to fix bugs.

If you enable "base files", you'll get two files looking something similar to: ```php // One being the base model which will be replaced with updates every time you run...

Would you mind sharing the error message you got, please? TIA.

This is a good case for a new feature, *supporting custom model names*. It'll be more tedious for the ones using it since they will have to add the mapping...

Wow! It seems you've got a huge database 😅 If you are using this on your local machine, you can [tweak](https://stackoverflow.com/a/5446042/7062181) you `php.ini` to allow for more memory usage.

This is weird. :thinking: If you want to generate a model for one table, you should use `php artisan code:models --table=password_reset`. However, my package tend to crush when a table...