fratzinger

+1. What about calling it `Arrayable`? This would follow `Promisable`.

What happens, if you search for `%joao%`?

Thanks for your quick response! Yep, it does. I've added this in a before-hook for multi-patches. Do you think this should stay as it is? for `find` the pagination is...

### @DaddyWarbucks It's totally a security issue. Maybe it's something for `disablePagination` from `feathers-hooks-common` (add `'patch'` to `checkContext`)? I understand the concerns. But patching the default amount of items and...

Good catch! We should add a test for that. Maybe even on `@feathersjs/adapter-tests` and we could add `$and` to the official supported operators list at https://docs.feathersjs.com/api/databases/querying.html. `Op.and` and `Op.or` can...

I have mixed feelings about this, too. I know scenarios where this definitely is a breaking change. My scenario is: On multi patch, use a before-hook with `find` (not explicitely...

don't forget about #363 and #364

https://github.com/feathersjs-ecosystem/feathers-sequelize/blob/db4b5ff9b89df9b163f9cd5d8c32de8c915ff71c/lib/index.js#L248 Should be `return Promise.resolve(id == null ? [] : null)` Same here: https://github.com/feathersjs-ecosystem/feathers-sequelize/blob/db4b5ff9b89df9b163f9cd5d8c32de8c915ff71c/lib/index.js#L300 Or should `$returning` only supported for `multi` requests? If so, we need to handle this as...

Can we keep them in the readme at the bottom under a `legacy` or `unmaintained` heading? So if anyone is interested in creating a new adapter that existed years before,...

how did you achieved this? Would you mind sharing a basic example?