Re: Adding Set as a SQL literal

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

Re: Prepared statements and INSERT INTO ... SELECT statements

That worked perfectly! Thank you! On Friday, April 6, 2018 at 4:22:57 PM UTC-5, Jeremy Evans wrote: > > On Friday, April 6, 2018 at 1:44:55 PM UTC-7, Ransom Briggs wrote: >> >> Hello, >> >> I have an insert statement that is inserting values selected from another >> table based on some filters.

Adding Set as a SQL literal

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

Re: Prepared statements and INSERT INTO ... SELECT statements

On Friday, April 6, 2018 at 1:44:55 PM UTC-7, Ransom Briggs wrote: > > Hello, > > I have an insert statement that is inserting values selected from another > table based on some filters. I am trying to convert this to a prepared > statement, but from what I can tell, the prepared statement

Prepared statements and INSERT INTO ... SELECT statements

Hello, I have an insert statement that is inserting values selected from another table based on some filters. I am trying to convert this to a prepared statement, but from what I can tell, the prepared statement version of insert