<    March 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 31
00:07 filterfish_ joined
00:26 GitHub100 joined
00:26 <GitHub100> [13sequel] 15jeremyevans pushed 2 new commits to 06master: 02https://git.io/vSep9
00:26 <GitHub100> 13sequel/06master 14b549ab6 15Jeremy Evans: Add deprecation message for using association_pks setter method without :delay_pks association option...
00:26 <GitHub100> 13sequel/06master 145129a4d 15Jeremy Evans: Deprecate calling Dataset#{update/delete/truncate} on datasets with limits or offsets unless the database supports it...
00:26 GitHub100 left
01:26 jaequery joined
02:24 jaequery joined
02:52 claw joined
02:59 claw joined
03:26 glennpratt joined
03:26 jaequery joined
03:33 glennpratt joined
03:34 jaequery joined
03:35 glennpra_ joined
03:41 glennpratt joined
03:52 filterfish joined
04:17 filterfish_ joined
04:18 glennpratt joined
04:18 filterfish_ joined
04:31 d762b440__ joined
07:27 glennpra_ joined
07:51 aidalgol joined
08:38 ta_ joined
08:48 ta_ joined
10:05 jeremyevans joined
11:24 pdrakeweb joined
13:56 banditron joined
15:41 riddley joined
15:42 <riddley> I'm having performance problems with MS SQL and my DBA has suggested that I use WITH NOLOCK on my joins as well as on the primary table... when I add .nolock to the end of the #left_join (etc) call, I only see the WITH NOLOCK on the primary table
15:43 <riddley> Is there something I should be doing differently?
15:50 <riddley> found this https://groups.google.com/forum/#!topic/sequel-talk/hc6KrMlH5Lk thanks
15:51 <riddley> oh, I (mistakenly?) thought that had the solution in it
15:59 brybeecher joined
16:36 <jeremyevans> riddley: What SQL do you want to generate?
16:37 <riddley> SELECT * FROM table1 a WITH (NOLOCK)
16:37 <riddley> INNER JOIN table2 b WITH (NOLOCK) ON a.ID = b.ID
16:37 <riddley> something like that
16:37 <riddley> although in reading more about this it seems like a can of worms
16:38 GitHub1 joined
16:38 <GitHub1> [13sequel] 15dadario opened pull request #1328: Schema dump ignoring database schema (06master...06master) 02https://git.io/vSf2u
16:38 GitHub1 left
16:40 GitHub28 joined
16:40 <GitHub28> [13sequel] 15jeremyevans commented on issue #1328: Thanks for the patch. I think this makes sense. Can you add a spec that checks that the :schema option is actually being passed? If not, I can do so when I merge. 02https://git.io/vSf2F
16:40 GitHub28 left
16:42 <jeremyevans> riddley: DB[Sequel[:table1].as(:a)].nolock.join(DB[Sequel[:table1]].nolock.as(:b), :id=>:id) # will be similar, but use a subselect
16:42 <jeremyevans> riddley: riddley: DB[Sequel[:table1].as(:a)].nolock.join(Sequel.lit('table2 b WITH (NOLOCK)'), Sequel[:b][:id]=>:id)
16:48 <riddley> tyvm!
16:57 <riddley> I tried to use the second one
16:57 <riddley> and the join syntax gets messed up
16:57 <riddley> oh
16:58 <riddley> I see
16:58 <riddley> I did it wrong
17:14 GitHub53 joined
17:14 <GitHub53> [13sequel] 15stereobooster opened pull request #1329: Dump collate for mysql (06master...06dump-collate-for-mysql) 02https://git.io/vSf6I
17:14 GitHub53 left
17:24 GitHub188 joined
17:24 <GitHub188> [13sequel] 15jeremyevans commented on issue #1329: I don't think it should be done at all in core Sequel, as it invites a slippery slope. There are many, many database-specific aspects that the schema dumper does not currently handle (e.g. functions, triggers, permissions), and trying to support them all is not feasible. If you are using database specific features, you should probably be using the database specific dump tools. 02https://git.io/
17:24 GitHub188 left
17:24 GitHub199 joined
17:24 <GitHub199> [13sequel] 15jeremyevans closed pull request #1329: Dump collate for mysql (06master...06dump-collate-for-mysql) 02https://git.io/vSf6I
17:24 GitHub199 left
17:25 Bish joined
17:41 tercenya_ joined
21:03 GitHub140 joined
21:03 <GitHub140> [13sequel] 15jeremyevans closed pull request #1328: Schema dump ignoring database schema (06master...06master) 02https://git.io/vSf2u
21:03 GitHub140 left
21:03 GitHub155 joined
21:03 <GitHub155> [13sequel] 15jeremyevans pushed 2 new commits to 06master: 02https://git.io/vSJcl
21:03 <GitHub155> 13sequel/06master 141782238 15Adriano Dadario: Schema dump ignoring database schema...
21:03 <GitHub155> 13sequel/06master 145d274a2 15Jeremy Evans: Add spec for that tests for :schema option usage in schema dumper...
21:03 GitHub155 left
21:18 mikhailvs joined
21:21 <mikhailvs> When my app runs and the internet connection drops out for a moment, is there a way to automatically reestablish the connection?
21:45 <jeremyevans> mikhailvs: Sequel should automatically remove a connection from the pool if there is a connection error, though an exception will be raised
21:45 <jeremyevans> mikhailvs: if you want to avoid the exception, you'll have to use the connection_validator extension
21:46 <mikhailvs> I'll give that a shot, thanks!
21:53 glennpratt joined
23:56 glennpratt joined