fermonkus

Activity Graph

Page 1 of 1

2016-07-26

[12:20:16] fermonkus: has joined #RubyOnRails
[15:35:37] fermonkus: Ping timeout: 252 seconds
[16:23:16] fermonkus: has joined #RubyOnRails
[16:33:55] fermonkus: Ping timeout: 250 seconds
[16:36:22] fermonkus: has joined #RubyOnRails
[18:30:15] fermonkus: Ping timeout: 244 seconds
[19:07:40] fermonkus: has joined #RubyOnRails
[23:30:35] fermonkus: Quit: Lost terminal

2016-07-20

[08:45:55] fermonkus: has joined #RubyOnRails
[11:17:43] fermonkus: Ping timeout: 252 seconds
[12:32:32] fermonkus: has joined #RubyOnRails
[15:02:22] fermonkus: Ping timeout: 258 seconds

2016-07-19

[08:34:55] fermonkus: has joined #RubyOnRails
[08:44:57] fermonkus: Ping timeout: 276 seconds
[08:55:41] fermonkus: has joined #RubyOnRails
[10:05:20] fermonkus: Ping timeout: 244 seconds
[10:28:29] fermonkus: has joined #RubyOnRails
[11:47:22] fermonkus: Ping timeout: 272 seconds
[11:58:51] fermonkus: has joined #RubyOnRails
[13:46:33] fermonkus: Ping timeout: 276 seconds

2016-07-15

[08:04:55] fermonkus: has joined #RubyOnRails
[10:09:32] fermonkus: Ping timeout: 260 seconds
[10:29:57] fermonkus: has joined #RubyOnRails
[12:25:40] fermonkus: Ping timeout: 264 seconds
[12:34:26] fermonkus: has joined #RubyOnRails
[13:11:11] fermonkus: Quit: leaving

2016-07-14

[07:59:09] fermonkus: has joined #RubyOnRails
[10:08:52] fermonkus: Ping timeout: 264 seconds
[10:31:34] fermonkus: has joined #RubyOnRails
[12:37:34] fermonkus: Ping timeout: 240 seconds
[13:02:13] fermonkus: has joined #RubyOnRails
[16:09:12] fermonkus: Ping timeout: 272 seconds
[17:39:46] fermonkus: has joined #RubyOnRails
[20:39:15] fermonkus: Ping timeout: 276 seconds
[20:53:04] fermonkus: has joined #RubyOnRails
[21:10:33] fermonkus: Ping timeout: 240 seconds
[22:01:02] fermonkus: has joined #RubyOnRails
[22:04:09] fermonkus: Client Quit

2016-07-13

[08:28:47] fermonkus: has joined #RubyOnRails
[10:07:24] fermonkus: Ping timeout: 246 seconds
[10:50:54] fermonkus: has joined #RubyOnRails
[16:05:12] fermonkus: Ping timeout: 276 seconds
[16:34:46] fermonkus: has joined #RubyOnRails
[16:39:19] fermonkus: Ping timeout: 250 seconds

2016-07-11

[16:43:03] fermonkus: has joined #RubyOnRails
[20:46:11] fermonkus: Ping timeout: 240 seconds
[21:37:59] fermonkus: has joined #RubyOnRails
[21:44:29] fermonkus: Quit: Lost terminal

2016-07-10

[09:07:55] fermonkus: has joined #RubyOnRails
[10:52:03] fermonkus: Quit: Lost terminal
[10:52:17] fermonkus: has joined #RubyOnRails
[11:13:26] fermonkus: In a situation where I'm defining a 'home' group for users (relationship is HMT on 'memberhsips' model) by adding a 'home' column to the memberships table, what reasons are there to use boolean vs binary?
[11:19:50] fermonkus: fox_mulder_cp: ok it sounds like that makes boolean the best option
[11:22:35] fermonkus: fox_mulder_cp: thanks. Would the best way to enforce only a single 'home' be to set default to false, and add logic in the controller/model to change it to True when a home is set (and convert any standing True state to False), or is there a better way?
[12:13:15] fermonkus: Ping timeout: 276 seconds
[13:56:07] fermonkus: has joined #RubyOnRails
[14:00:44] fermonkus: Ping timeout: 258 seconds
[15:44:20] fermonkus: has joined #RubyOnRails
[15:49:24] fermonkus: Ping timeout: 272 seconds
[16:32:38] fermonkus: has joined #RubyOnRails
[20:19:51] fermonkus: Ping timeout: 258 seconds
[20:51:48] fermonkus: has joined #RubyOnRails
[21:39:38] fermonkus: Ping timeout: 272 seconds
[21:44:18] fermonkus: has joined #RubyOnRails
[21:50:31] fermonkus: Ping timeout: 244 seconds

2016-07-09

[20:49:08] fermonkus: has joined #RubyOnRails
[23:57:38] fermonkus: Quit: Lost terminal

2016-07-08

[06:52:47] fermonkus: has joined #RubyOnRails
[10:35:40] fermonkus: Ping timeout: 258 seconds
[11:07:18] fermonkus: has joined #RubyOnRails
[13:38:57] fermonkus: Ping timeout: 246 seconds

2016-07-07

[07:50:16] fermonkus: has joined #RubyOnRails
[12:40:25] fermonkus: Ping timeout: 244 seconds
[13:01:33] fermonkus: has joined #RubyOnRails
[16:07:36] fermonkus: Ping timeout: 244 seconds

2016-07-06

[14:38:03] fermonkus: has joined #RubyOnRails
[16:00:33] fermonkus: Ping timeout: 240 seconds
[16:43:07] fermonkus: has joined #RubyOnRails
[18:06:31] fermonkus: Ping timeout: 240 seconds
[19:28:37] fermonkus: has joined #RubyOnRails
[21:19:43] fermonkus: Ping timeout: 252 seconds
[21:53:39] fermonkus: has joined #RubyOnRails
[22:27:03] fermonkus: Quit: Lost terminal

2016-07-05

[12:44:44] fermonkus: has joined #RubyOnRails
[16:20:52] fermonkus: Ping timeout: 264 seconds
[18:28:32] fermonkus: has joined #RubyOnRails
[18:47:11] fermonkus: To go off tyul's question, I've got a similar situation in that I have users that join Clubs, which is done through a Membership model (user_clubs)... I was planning on just adding a "home_club" attribute to the Memberships model to indicate the user's main Club. Sensible?
[18:47:49] fermonkus: "home_club" being boolean
[18:48:33] fermonkus: dminuoso: thanks, will look into that!
[20:57:15] fermonkus: Ping timeout: 250 seconds
[22:06:38] fermonkus: has joined #RubyOnRails
[22:06:54] fermonkus: Client Quit

2016-06-24

[07:48:40] fermonkus: has joined #RubyOnRails
[09:16:34] fermonkus: Ping timeout: 240 seconds
[09:35:34] fermonkus: has joined #RubyOnRails
[10:38:27] fermonkus: Ping timeout: 276 seconds
[15:58:23] fermonkus: has joined #RubyOnRails
[16:29:39] fermonkus: Ping timeout: 260 seconds

2016-06-23

[08:54:26] fermonkus: has joined #RubyOnRails
[09:26:00] fermonkus: Ping timeout: 246 seconds
[09:27:58] fermonkus: has joined #RubyOnRails
[11:13:40] fermonkus: Ping timeout: 272 seconds

2016-06-22

[08:05:50] fermonkus: has joined #RubyOnRails
[10:07:51] fermonkus: Ping timeout: 240 seconds
[10:39:55] fermonkus: has joined #RubyOnRails
[12:51:11] fermonkus: Ping timeout: 240 seconds
[12:55:20] fermonkus: has joined #RubyOnRails
[16:15:31] fermonkus: Ping timeout: 240 seconds

2016-06-21

[07:47:18] fermonkus: has joined #RubyOnRails
[11:47:27] fermonkus: Ping timeout: 276 seconds
[12:59:04] fermonkus: has joined #RubyOnRails
[14:15:44] fermonkus: Ping timeout: 244 seconds
[14:49:39] fermonkus: has joined #RubyOnRails
[15:32:21] fermonkus: Ping timeout: 276 seconds

2016-06-20

[08:10:13] fermonkus: has joined #RubyOnRails
[08:55:24] fermonkus: Ping timeout: 260 seconds
[08:55:52] fermonkus: has joined #RubyOnRails
[10:17:28] fermonkus: Ping timeout: 252 seconds
[10:26:10] fermonkus: has joined #RubyOnRails
[11:07:13] fermonkus: Ping timeout: 244 seconds
[11:41:25] fermonkus: has joined #RubyOnRails
[15:56:54] fermonkus: Ping timeout: 244 seconds
[16:26:30] fermonkus: has joined #RubyOnRails
[17:11:48] fermonkus: Ping timeout: 258 seconds

2016-06-18

[12:52:26] fermonkus: has joined #RubyOnRails
[12:54:25] fermonkus: Guys, big rails (and development in genral) noob here... what do I do if rake test returns a segfault?
[12:55:54] fermonkus: Whoops, sorry everyone, didn't mean to be exclusionary. Apologies
[12:58:21] fermonkus: matthewd: I think so
[12:58:36] fermonkus: error is in variable_name_check.rb
[13:01:12] fermonkus: matthewd: thanks, I'll have a poke around, helps a lot to be pointed in the right direction
[13:05:58] fermonkus: matthewd: fairly small app, I suspect it might be a problem with Nokogiri, since that's giving me trouble with bundle install
[13:30:04] fermonkus: Quit: Lost terminal

2016-06-17

[12:46:10] fermonkus: has joined #RubyOnRails
[15:31:55] fermonkus: Ping timeout: 244 seconds
[15:32:21] fermonkus: has joined #RubyOnRails
[15:43:51] fermonkus: Read error: Connection reset by peer
[16:14:36] fermonkus: has joined #RubyOnRails
[19:44:01] fermonkus: Ping timeout: 244 seconds

2016-01-23

[16:30:26] fermonkus: has joined #ruby
[18:05:43] fermonkus: Quit: Lost terminal