To make it work, you need to:
- Enable the extension prior to defining the FooModel class
- Run the paginate method on the model dataset with
FooModel.dataset.paginate(1,2)
I'm not sure if there's a reason why the model doesn't proxy the paginate
method to its underlying dataset.
Best
Em dom., 2
I've tried loading the extension before defining models, it doesn't work.
And I tried calling dataset on the model and pagination on it - that
doesn't work either.
The only thing that works is pagination directly on the db schema -
```ruby
DB[:foo_models].paginate(1,2)
```
понедельник, 23 августа
On Mon, Aug 23, 2021 at 12:13 AM Marcelo Pereira <
marcelovitor.pere...@gmail.com> wrote:
> To make it work, you need to:
> - Enable the extension prior to defining the FooModel class
> - Run the paginate method on the model dataset with
> FooModel.dataset.paginate(1,2)
>
> I'm not sure if there's
Thanks
понедельник, 23 августа 2021 г. в 17:31:28 UTC+3, Jeremy Evans:
> On Mon, Aug 23, 2021 at 12:13 AM Marcelo Pereira
> wrote:
>
>> To make it work, you need to:
>> - Enable the extension prior to defining the FooModel class
>> - Run the paginate method on the model dataset with
>> FooMod
I appreciate that :generated is being included in column schema hashes, as
of 5.31.0.
Are there any plans to add creating generated columns in migrations? Or
does this exist as an extension and my Googling/research efforts are
failing?
Thanks,
Drew
--
You received this message because you a
On Mon, Aug 23, 2021 at 10:41 AM Drew Breunig wrote:
> I appreciate that :generated is being included in column schema hashes, as
> of 5.31.0.
>
> Are there any plans to add creating generated columns in migrations? Or
> does this exist as an extension and my Googling/research efforts are
> faili
