Sam

its tricky, how would we easily know something is binary data? for starters though can you add a note to the readme?

Hmmm ... maybe we support: `conn.auto_encode_arrays!` Then you would not need `.array` calls if you are careful with your usage.

understood, my thinking is that `conn.auto_encode_arrays!` would be something you enable if you are just about to start a brand new project and saves you ceremony.

Is there any downside to doing this 100% automatically, if we see an Array in the param we just use encode array? What can break with a change like that?

Can you include and specific examples of what you did and a repro. It is extremely unexpected for mini_sql to be slower than rails under any conditions, for identical queries.

Yes, have a look at Discourse source for an example, we should add to the readme On Wed, 24 Mar 2021 at 8:00 pm, Simon ***@***.***> wrote: > When I...

not sure what is left here, closing

I started discussing @georgeclaghorn My long term thinking here. - Move discourse/mini_mime to rails/mini_mime ... - Merge marcel into mini_mime so mini_mime can also do lookup by file content -...

So sorry .. .this has dropped off my list. My general thinking is that I just wanted 100% parity and was totally happy for mime-types to set the priority rules....

Fundamentally you are going to end up picking "one thing" so the interface of "please give me a mime type for X" is still correct imo. I do support adding...