solenoids

Activity Graph

Page 1 of 1

2016-01-23

[04:36:36] solenoids: Ping timeout: 256 seconds

2016-01-11

[13:01:34] solenoids: Ping timeout: 256 seconds
[13:15:21] solenoids: has joined #ruby
[19:44:06] solenoids: Ping timeout: 240 seconds
[20:01:52] solenoids: has joined #ruby

2016-01-10

[02:31:21] solenoids: Ping timeout: 255 seconds
[02:45:48] solenoids: has joined #ruby
[11:40:35] solenoids: Ping timeout: 245 seconds
[11:57:34] solenoids: has joined #ruby

2016-01-05

[15:41:55] solenoids: Ping timeout: 240 seconds
[15:56:11] solenoids: has joined #ruby
[16:10:59] solenoids: Ping timeout: 264 seconds
[16:28:21] solenoids: has joined #ruby

2016-01-02

[00:00:53] solenoids: Ping timeout: 240 seconds
[00:26:00] solenoids: has joined #ruby

2015-12-25

[00:23:30] solenoids: Ping timeout: 245 seconds
[00:37:40] solenoids: has joined #ruby
[07:40:50] solenoids: Ping timeout: 256 seconds
[07:57:11] solenoids: has joined #ruby

2015-12-24

[16:21:00] solenoids: Ping timeout: 245 seconds
[16:36:04] solenoids: has joined #ruby
[20:47:02] solenoids: Ping timeout: 250 seconds
[21:06:32] solenoids: has joined #ruby

2015-12-23

[04:22:26] solenoids: Ping timeout: 240 seconds
[04:36:00] solenoids: has joined #ruby
[10:47:38] solenoids: Ping timeout: 272 seconds
[11:05:26] solenoids: has joined #ruby

2015-12-17

[05:04:49] solenoids: what's the best drop-in ruby interpreter for optimizing memory usage? would jruby be the best option, ignoring the initial JVM overhead?

2015-12-15

[03:30:56] solenoids: Ping timeout: 272 seconds
[03:34:18] solenoids: has joined #ruby

2015-12-07

[21:23:47] solenoids: Ping timeout: 260 seconds

2015-12-06

[14:56:49] solenoids: Ping timeout: 245 seconds
[14:58:17] solenoids: has joined #ruby
[14:58:18] solenoids: has joined #RubyOnRails
[15:07:30] solenoids: Ping timeout: 260 seconds
[15:30:35] solenoids: has joined #ruby
[15:30:43] solenoids: has joined #RubyOnRails

2015-12-05

[00:55:43] solenoids: Ping timeout: 260 seconds
[01:08:38] solenoids: has joined #ruby
[01:08:46] solenoids: has joined #RubyOnRails
[07:43:35] solenoids: Ping timeout: 260 seconds
[08:00:39] solenoids: has joined #ruby
[08:00:47] solenoids: has joined #RubyOnRails

2015-12-04

[22:24:44] solenoids: Ping timeout: 245 seconds
[22:38:37] solenoids: has joined #ruby
[22:38:45] solenoids: has joined #RubyOnRails

2015-12-02

[15:35:54] solenoids: *.net *.split
[16:28:43] solenoids: has joined #RubyOnRails
[16:28:45] solenoids: has joined #ruby

2015-12-01

[01:50:18] solenoids: Ping timeout: 250 seconds

2015-11-30

[15:31:17] solenoids: Ping timeout: 246 seconds
[15:45:12] solenoids: has joined #ruby
[15:45:20] solenoids: has joined #RubyOnRails
[17:09:54] solenoids: Ping timeout: 260 seconds
[17:23:38] solenoids: has joined #ruby
[17:23:46] solenoids: has joined #RubyOnRails

2015-11-29

[11:20:50] solenoids: Ping timeout: 240 seconds
[11:35:53] solenoids: has joined #ruby
[11:36:01] solenoids: has joined #RubyOnRails
[15:22:54] solenoids: Ping timeout: 260 seconds
[15:39:31] solenoids: has joined #ruby
[15:39:39] solenoids: has joined #RubyOnRails

2015-11-26

[09:23:50] solenoids: Ping timeout: 240 seconds
[09:39:01] solenoids: has joined #ruby
[12:30:14] solenoids: Ping timeout: 276 seconds
[12:45:45] solenoids: has joined #ruby
[16:19:00] solenoids: has joined #RubyOnRails
[16:20:37] solenoids: in my migrations, if I have a table `posts` that belongs_to a `user`, should I also put a has_many in the `users` schema?
[16:21:12] solenoids: will doing this essentially just cache a list of all posts on each user row?
[16:40:36] solenoids: in the migration that creates the schema
[16:41:48] solenoids: I tested it out and it stores the relationship as an index
[16:42:26] solenoids: hmm? I assumed relationships have to be defined in the schema, too
[16:42:36] solenoids: http://guides.rubyonrails.org/association_basics.html
[16:43:42] solenoids: it makes an index named "index_posts_on_user_id", which your model detects and uses
[16:43:54] solenoids: from what I see
[16:46:24] solenoids: interesting, it works without the relationship being defined in the schema?
[16:46:33] solenoids: wonder how it's storing it
[16:46:52] solenoids: I just started learning RoR this morning :P
[16:50:55] solenoids: so the model just inserts the necessary columns for relationships?
[16:54:12] solenoids: well yeah, you define the relationship in the actual model class
[16:54:27] solenoids: I just didn't know doing that would change the actual schema
[17:02:33] solenoids: goldbug: unsure about terminology here, do you mean relationships should be defined only in app/models/*.rb and not db/migrate/*.rb?
[19:01:52] solenoids: *.net *.split
[19:08:04] solenoids: has joined #ruby
[19:08:08] solenoids: has joined #RubyOnRails
[19:09:22] solenoids: Max SendQ exceeded
[19:10:34] solenoids: has joined #ruby
[19:10:42] solenoids: has joined #RubyOnRails

2015-11-25

[05:16:11] solenoids: Ping timeout: 260 seconds
[05:34:24] solenoids: has joined #ruby

2015-11-24

[07:26:00] solenoids: Ping timeout: 265 seconds
[07:42:03] solenoids: has joined #ruby
[21:04:59] solenoids: Ping timeout: 264 seconds
[21:18:05] solenoids: has joined #ruby

2015-11-23

[21:40:02] solenoids: Ping timeout: 250 seconds
[21:54:00] solenoids: has joined #ruby

2015-11-22

[03:45:51] solenoids: *.net *.split
[04:11:12] solenoids: has joined #ruby

2015-11-20

[16:42:55] solenoids: Ping timeout: 265 seconds
[16:57:15] solenoids: has joined #ruby
[19:42:07] solenoids: Ping timeout: 260 seconds
[19:58:56] solenoids: has joined #ruby

2015-11-17

[00:03:19] solenoids: Ping timeout: 240 seconds
[02:43:49] solenoids: Ping timeout: 244 seconds
[02:57:31] solenoids: has joined #ruby
[03:53:25] solenoids: Ping timeout: 265 seconds
[04:08:19] solenoids: has joined #ruby
[06:31:06] solenoids: Ping timeout: 250 seconds
[06:44:33] solenoids: has joined #ruby
[10:49:47] solenoids: Ping timeout: 276 seconds
[11:05:21] solenoids: has joined #ruby
[15:10:14] solenoids: Ping timeout: 272 seconds
[15:23:30] solenoids: has joined #ruby
[20:38:11] solenoids: Ping timeout: 260 seconds
[20:55:33] solenoids: has joined #ruby

2015-11-16

[13:02:07] solenoids: Ping timeout: 260 seconds
[13:17:18] solenoids: has joined #ruby

2015-11-12

[04:44:07] solenoids: has joined #ruby

2015-11-11

[04:27:39] solenoids: Ping timeout: 240 seconds

2015-11-10

[19:07:29] solenoids: Ping timeout: 265 seconds
[19:21:02] solenoids: has joined #ruby
[20:48:24] solenoids: Ping timeout: 240 seconds
[21:03:05] solenoids: has joined #ruby
[23:11:46] solenoids: Ping timeout: 244 seconds
[23:28:34] solenoids: has joined #ruby

2015-11-09

[08:38:30] solenoids: Ping timeout: 240 seconds
[08:53:45] solenoids: has joined #ruby
[14:23:35] solenoids: Ping timeout: 264 seconds
[14:40:53] solenoids: has joined #ruby

2015-11-08

[13:37:20] solenoids: Ping timeout: 244 seconds
[13:51:45] solenoids: has joined #ruby
[15:09:33] solenoids: Ping timeout: 255 seconds
[15:26:32] solenoids: has joined #ruby

2015-11-06

[16:28:55] solenoids: Ping timeout: 260 seconds
[16:42:36] solenoids: has joined #ruby
[20:21:26] solenoids: Ping timeout: 240 seconds
[20:39:13] solenoids: has joined #ruby

2015-11-04

[05:13:07] solenoids: has joined #ruby

2015-10-30

[03:29:11] solenoids: Ping timeout: 256 seconds
[03:42:30] solenoids: has joined #ruby
[06:40:46] solenoids: Ping timeout: 240 seconds

2015-10-26

[08:10:54] solenoids: Ping timeout: 268 seconds
[08:28:02] solenoids: has joined #ruby

2015-10-25

[21:40:04] solenoids: has joined #ruby

2015-10-24

[19:54:59] solenoids: Ping timeout: 250 seconds

2015-10-23

[03:44:47] solenoids: Ping timeout: 250 seconds
[03:58:33] solenoids: has joined #ruby
[11:52:39] solenoids: Ping timeout: 260 seconds
[12:09:33] solenoids: has joined #ruby

2015-10-20

[22:31:46] solenoids: has joined #ruby