This is how I've been using it, now currently replaced with "30 days"
manually. I'd like to shove a variable in there.
tm = PG::TypeMapByColumn.new([
PG::TextEncoder::String.new
])
d = d.to_s
res = $conn.exec_params( %Q{ SELECT search_phrase, count(search_phrase)
FROM searches
Hi. Sorry for the delay. Fighting a now 4-week cold, been out of
commission.
Been reading and testing some more, translating my current projects. I try
to post generalized examples as this isn't about anything specific.
--
You received this message because you are subscribed to the
No strong feelings either way; when I run Sequel tests I'm normally
authoring a patch, which means I have the git repository anyways. I have to
wonder how frequently the tests in the gem are being run tho.
That said, I can imagine the tests in something with a C extension (such as
sequel_pg)
I've never run the Sequel tests, so I'm fine with them not being included
in the gem. The source can anyway be downloaded if testing is to be done.
- Abhijit.
On Sun, Jan 19, 2020 at 12:57 AM Jeremy Evans
wrote:
> Sequel has always shipped tests in the gem, so that users and packagers
> can
I would guess most of the time users are not running Sequel tests and, if
one wants to run them, it's simple enough to clone the repository - so I
would say not shipping the tests sounds like a good idea. No strong
opinions on this one, though - having the tests in the gem is, of course,
not a
