<    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 25 26 27 28 29  
30
00:11 glennpratt joined
00:53 glennpratt joined
01:12 glennpratt joined
01:26 glennpratt joined
03:08 jeremyevans_ joined
04:21 glennpratt joined
05:36 glennpratt joined
06:31 bawigga joined
06:37 glennpratt joined
06:38 glennpratt joined
07:59 jaequery joined
08:34 GitHub98 joined
08:34 <GitHub98> [13sequel] 15perlun opened issue #1335: as400 jdbc adapter does not honor identifier_mangling: false 02https://git.io/vSPrg
08:34 GitHub98 left
08:42 aidalgol joined
09:00 glennpratt joined
09:34 lopex joined
11:34 glennpratt joined
16:00 glennpratt joined
16:02 glennpra_ joined
17:15 glennpratt joined
17:18 glennpratt joined
17:30 GitHub124 joined
17:30 <GitHub124> [13sequel] 15jeremyevans commented on issue #1335: Note that `:identifier_mangling => false` Database option does not mean no identifier mangling, it means don't load the identifier_mangling extension (technically, now the _deprecated_identifier_mangling extension). The default in Sequel for databases that fold unquoted identifiers to uppercase is to upcase on input and downcase on output. The default in Sequel for databases that fold unquoted id
17:30 GitHub124 left
17:30 GitHub113 joined
17:30 <GitHub113> [13sequel] 15jeremyevans closed issue #1335: as400 jdbc adapter does not honor identifier_mangling: false 02https://git.io/vSPrg
17:30 GitHub113 left
17:47 ben___ joined
17:53 jaequery joined
18:24 bedmonds joined
19:59 ben_____ joined
20:28 banditron joined
21:00 tercenya joined
21:36 banditron joined
21:47 <jaequery> is there a way to perform case insensitive searches?
21:47 <jaequery> only thing i see is ILIKE but i dont wanna perform a LIKE query
21:49 <jaequery> in fact i can even live with making every queries case-insensitive by default, like mysql does
21:51 <jeremyevans_> jaequery: depends on the database. There is always the lower() database function
21:52 <jeremyevans_> jaequery: on PostgreSQL, there is the citext type in contrib for a case insensitive string field
22:05 <jaequery> hm, so there is no easy way to do this in sequel besides using ILIKE ?
22:06 <jaequery> i guess i'll try lower for now
22:06 <jeremyevans_> jaequery: I just said, you can use the lower database function if you don't want to use LIKE/ILIKE: where{{lower(:column)=>lower('value')}}
22:07 <jaequery> yea, gotcha. thanks jeremy
22:12 <jaequery> sorry but that makes me question, what is the difference between, where{ ... } , and where {{ .... }} ?
22:20 <jeremyevans_> jaequery: where{} uses a virtual row block, where{{}} is a hash inside a virtual row block
22:22 mahlon joined
22:45 <Rennex> oh, never seen that before. doesn't where{lower(:column) == lower('value")} work?
22:45 <Rennex> aside from the quote mismatch :P
22:47 <jeremyevans_> Rennex: nope. You can use =~ though
22:48 <jeremyevans_> Rennex: overriding == is a bit too extreme
23:03 <Rennex> jeremyevans_: oh, i never felt so, in a context where you can just make up method names and they appear from the ether ;)
23:11 <Rennex> jeremyevans_: i don't know if people really use those SQL::Identifiers etc in other contexts than virtual rows... but for me, virtual rows are the main use case and not having a simple == work is a bummer. How about if virtual row blocks gave you special subclasses of identifier objects that have == overridden? Then anyone making normal SQL::Identifiers would be exempt