<    April 2017    >
Su Mo Tu We Th Fr Sa  
                   1  
 2  3  4  5  6  7  8  
 9 10 11 12 13 14 15  
16 17 18 19 20 21 22  
23 24 _2_5 26 27 28 29  
30
02:15 nirvdrum joined
04:25 nirvdrum joined
07:00 riddley joined
07:46 jaequery joined
08:32 aidalgol joined
09:22 ben__ joined
10:21 ben__ joined
13:27 ben__ joined
13:29 ben__ joined
13:48 banditron joined
13:55 ben__ joined
16:06 GitHub53 joined
16:06 <GitHub53> [13sequel] 15jeremyevans pushed 5 new commits to 06master: 02https://git.io/v9J0m
16:06 <GitHub53> 13sequel/06master 148908bb1 15Jeremy Evans: Deprecate using a joined dataset as a Sequel::Model dataset...
16:06 <GitHub53> 13sequel/06master 14a506e89 15Jeremy Evans: Avoid use of virtual row method block in hsqldb adapter
16:06 <GitHub53> 13sequel/06master 14f55bbe1 15Jeremy Evans: Don't use virtual row method block in row number offset emulation
16:06 GitHub53 left
16:27 riddley joined
16:35 jaequery joined
16:36 ben_____ joined
17:55 <mahlon> Hm. Any special tricks for postgresql pg_trgm selects on a dataset? I'm getting an error when trying, but the SQL that sequel generates can be copy/pasted into psql and it works fine.
17:55 <mahlon> db[ :pg_extension ].select_map( :extname ) #=> ["plpgsql", "pg_trgm"]
17:55 <mahlon> db[ :apps__words ].where( Sequel.lit("word % ?", term) ).reverse_order{ similarity:)word, term) }.all
17:55 <mahlon> Sequel::DatabaseError: PG::UndefinedFunction: ERROR: operator does not exist: text % unknown
17:55 <mahlon> LINE 1: SELECT * FROM "apps"."words" WHERE word % 'johnathan' ORDER ...
17:56 <mahlon> Eh, weird paste there with my parens, assume those are fine. :)
18:13 <jeremyevans> mahlon: try: Sequel.lit("word % ?::text", term) and see if it makes a difference
18:19 <mahlon> jeremyevans: Same result, but different error: ERROR: operator does not exist: text % text and LINE 1: SELECT * FROM "apps"."words" WHERE word % 'johnathan'::text ...
18:20 <mahlon> Which is interesting... \do on % definitely has text/text for left/right arg types, respectively.
18:22 <jeremyevans> mahlon: can you try using ruby-pg directly and see if the problem occurs there?
18:23 <mahlon> Will do.
21:48 Renich joined
21:56 <mahlon> Same issues, but put me on the right track. The CREATE EXTENSION step was done in a schema instead of public, so the operators weren't available. Nothing to see here. Lookin' good.