Re: Adding Set as a SQL literal

2018-04-06 Thread Jeremy Evans
On Friday, April 6, 2018 at 2:53:01 PM UTC-7, Ransom Briggs wrote:
>
> I have a query where I do some pre processing with a Set to eliminate 
> duplicates and am converting to an array to avoid this error.
>
> *** Sequel::Error Exception: can't express # as a SQL literal
>
> I peeked at the code and adding it as a supported type did not look too 
> hard.  If I put together a PR, would this be something of interest?
>

No. Set is in ruby stdlib, but not in ruby core and not required by sequel 
itself, so I don't think it is appropriate to add.  This is something 
should be added as an external extension if you would like others to be 
able to use it.

Thanks,
Jeremy

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sequel-talk+unsubscr...@googlegroups.com.
To post to this group, send email to sequel-talk@googlegroups.com.
Visit this group at https://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.


Adding Set as a SQL literal

2018-04-06 Thread Ransom Briggs
I have a query where I do some pre processing with a Set to eliminate 
duplicates and am converting to an array to avoid this error.

*** Sequel::Error Exception: can't express # as a SQL literal

I peeked at the code and adding it as a supported type did not look too 
hard.  If I put together a PR, would this be something of interest?

Thanks,
Ransom

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sequel-talk+unsubscr...@googlegroups.com.
To post to this group, send email to sequel-talk@googlegroups.com.
Visit this group at https://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.