Updates from toksyuryel on Rainbow Dash Network!
toksyuryel: This is helpful http://blog.sanctum.geek.nz/vim-misconceptions/ !coderpony
toksyuryel's status on Wednesday, 01-Aug-12 15:09:40 UTC
This is helpful http://blog.sanctum.geek.nz/vim-misconceptions/ !coderpony
toksyuryel: So can someone maybe explain closures to me in as few buzzwords as possible? !coderpony
toksyuryel's status on Tuesday, 31-Jul-12 14:46:03 UTC
So can someone maybe explain closures to me in as few buzzwords as possible? !coderpony
toksyuryel: Another great article from Eevee http://me.veekun.com/blog/2012/07/28/quick-doesnt-mean-dirty/ (as usual, lots of #NSFW language here) !coderpony
toksyuryel's status on Tuesday, 31-Jul-12 13:43:22 UTC
Another great article from Eevee http://me.veekun.com/blog/2012/07/28/quick-doesnt-mean-dirty/ (as usual, lots of #NSFW language here) !coderpony
toksyuryel: @minti @widget Come play !sk with me and @bitshift so we can have the whole #coderpony crew on at once :D
toksyuryel's status on Monday, 23-Jul-12 20:06:20 UTC
@minti @widget Come play !sk with me and @bitshift so we can have the whole #coderpony crew on at once :D
toksyuryel: Before I go to bed, I wanted to share this because it makes me happy. http://dpaste.com/749403/ @widget @bitshift !coderpony #SQL
toksyuryel's status on Thursday, 17-May-12 16:31:19 UTC
Before I go to bed, I wanted to share this because it makes me happy. http://dpaste.com/749403/ @widget @bitshift !coderpony #SQL
toksyuryel: @aeniug2 You should join !coderpony
toksyuryel's status on Wednesday, 16-May-12 03:21:49 UTC
@aeniug2 You should join !coderpony
toksyuryel: Pre-caching the path instead of generating it dynamically seems to only improve cached performance (though the improvement there is dramatic). In some cases the uncached performance was actually *worse* than generating the path in a WITH RECURSIVE block. http://pgsql.privatepaste.com/60741d539f @bitshift @widget !coderpony #SQL
toksyuryel's status on Monday, 14-May-12 09:32:33 UTC
Pre-caching the path instead of generating it dynamically seems to only improve cached performance (though the improvement there is dramatic). In some cases the uncached performance was actually *worse* than generating the path in a WITH RECURSIVE block. http://pgsql.privatepaste.com/60741d539f @bitshift @widget !coderpony #SQL
toksyuryel: So, first test: building the paths in a WITH RECURSIVE block under normal settings. Test shows that this is, indeed, unacceptably slow but cached performance is phenomenal until the thread gets monstrously huge; as real world threads will never get as big as even the smallest thread in this sample, and certainly won't be so spread out, I consider the cached performance to be acceptable but I'd like something better for uncached performance. Now let's test it with the pre-computed paths. http://pgsql.privatepaste.com/205d6138f2 @bitshift @widget !coderpony #SQL
toksyuryel's status on Monday, 14-May-12 09:10:37 UTC
So, first test: building the paths in a WITH RECURSIVE block under normal settings. Test shows that this is, indeed, unacceptably slow but cached performance is phenomenal until the thread gets monstrously huge; as real world threads will never get as big as even the smallest thread in this sample, and certainly won't be so spread out, I consider the cached performance to be acceptable but I'd like something better for uncached performance. Now let's test it with the pre-computed paths. http://pgsql.privatepaste.com/205d6138f2 @bitshift @widget !coderpony #SQL
toksyuryel: Hm, that was done faster than I thought. I estimated the total size would get to be over 5GB but it only got to 4.1GB before it finished. Here's an hour-by-hour breakdown of how long it took to populate the database with over ten million rows: http://dpaste.com/747878/ !coderpony #SQL
toksyuryel's status on Monday, 14-May-12 08:23:58 UTC
Hm, that was done faster than I thought. I estimated the total size would get to be over 5GB but it only got to 4.1GB before it finished. Here's an hour-by-hour breakdown of how long it took to populate the database with over ten million rows: http://dpaste.com/747878/ !coderpony #SQL
toksyuryel: I can't understand what this error is about. All of my parenthesis seem to line up properly (and it successfully creates the first two tables before the one with the error) and I don't see any misplaced or missing semicolons. Any help? http://dpaste.com/747347/ @bitshift @widget !coderpony #SQL
toksyuryel's status on Sunday, 13-May-12 01:13:01 UTC
I can't understand what this error is about. All of my parenthesis seem to line up properly (and it successfully creates the first two tables before the one with the error) and I don't see any misplaced or missing semicolons. Any help? http://dpaste.com/747347/ @bitshift @widget !coderpony #SQL
toksyuryel: Here's a comparison of uncached performance vs cached performance http://dpaste.com/747276/ @bitshift @widget !coderpony #SQL
toksyuryel's status on Saturday, 12-May-12 20:37:27 UTC
Here's a comparison of uncached performance vs cached performance http://dpaste.com/747276/ @bitshift @widget !coderpony #SQL
toksyuryel: I'm pretty happy about this. http://dpaste.com/746779/ @widget @bitshift !coderpony #SQL
toksyuryel's status on Friday, 11-May-12 19:14:58 UTC
I'm pretty happy about this. http://dpaste.com/746779/ @widget @bitshift !coderpony #SQL
toksyuryel: A question arises: if a column references its own table as a foreign key with ON DELETE RESTRICT and just so happens to refer to its own row, is that row simply completely impossible to delete or will it be deleted normally? !coderpony #SQL
toksyuryel's status on Thursday, 10-May-12 00:42:11 UTC
A question arises: if a column references its own table as a foreign key with ON DELETE RESTRICT and just so happens to refer to its own row, is that row simply completely impossible to delete or will it be deleted normally? !coderpony #SQL
toksyuryel: Today's lesson: arrays are evil. http://dpaste.com/745811/ @bitshift !coderpony #SQL
toksyuryel's status on Thursday, 10-May-12 00:31:17 UTC
Today's lesson: arrays are evil. http://dpaste.com/745811/ @bitshift !coderpony #SQL
toksyuryel: @bitshift I dunno, I designed half of it while half asleep anyway. Here it is anyway for your perusal http://dpaste.com/745314/ (to anyone just joining us, I'm learning all of this as I go and currently lack the means to test whether I've gotten any of this right, so if the syntax and such is completely wrong it's because I have no idea what I'm doing) !coderpony #SQL
toksyuryel's status on Wednesday, 09-May-12 05:34:44 UTC
@bitshift I dunno, I designed half of it while half asleep anyway. Here it is anyway for your perusal http://dpaste.com/745314/ (to anyone just joining us, I'm learning all of this as I go and currently lack the means to test whether I've gotten any of this right, so if the syntax and such is completely wrong it's because I have no idea what I'm doing) !coderpony #SQL
toksyuryel: @bitshift So how'd I do? :) http://dpaste.com/745233/ !coderpony #SQL
toksyuryel's status on Wednesday, 09-May-12 00:47:20 UTC
@bitshift So how'd I do? :) http://dpaste.com/745233/ !coderpony #SQL
toksyuryel: @toksyuryel @bitshift I realized I forgot some conditionals in one of the stubbed functions, here's a fixed version of that http://dpaste.com/745201/ !coderpony #SQL
toksyuryel's status on Tuesday, 08-May-12 23:10:58 UTC
@toksyuryel @bitshift I realized I forgot some conditionals in one of the stubbed functions, here's a fixed version of that http://dpaste.com/745201/ !coderpony #SQL
toksyuryel: @bitshift I have stubbed out several functions and created the triggers to demonstrate how I plan to constrain the arrays http://dpaste.com/745194/ !coderpony #SQL
toksyuryel's status on Tuesday, 08-May-12 23:05:16 UTC
@bitshift I have stubbed out several functions and created the triggers to demonstrate how I plan to constrain the arrays http://dpaste.com/745194/ !coderpony #SQL
toksyuryel: @bitshift Let's see how horribly I botched this one up http://dpaste.com/745169/ !coderpony #SQL
toksyuryel's status on Tuesday, 08-May-12 22:09:18 UTC
@bitshift Let's see how horribly I botched this one up http://dpaste.com/745169/ !coderpony #SQL
toksyuryel: @bitshift http://dpaste.com/745125/ here's what it looks like now !coderpony #SQL
toksyuryel's status on Tuesday, 08-May-12 20:50:47 UTC
@bitshift http://dpaste.com/745125/ here's what it looks like now !coderpony #SQL
toksyuryel: @bitshift As long as I'm using dpaste I might as well just post the entire file. Let me know how much I screwed everything up! http://dpaste.com/745106/ !coderpony #SQL
toksyuryel's status on Tuesday, 08-May-12 20:34:16 UTC
@bitshift As long as I'm using dpaste I might as well just post the entire file. Let me know how much I screwed everything up! http://dpaste.com/745106/ !coderpony #SQL
toksyuryel: Did I do this right? ` replyto bigint CHECK (replyto IS NOT postid AND replyto IS CASE WHEN conversation IS NOT postid THEN NOT NULL),` !coderpony #SQL
toksyuryel's status on Tuesday, 08-May-12 20:19:16 UTC
Did I do this right? ` replyto bigint CHECK (replyto IS NOT postid AND replyto IS CASE WHEN conversation IS NOT postid THEN NOT NULL),` !coderpony #SQL
toksyuryel: Using PostgreSQL, can a foreign key reference the table it appears in? Or is there some other way to do this? !coderpony #SQL
toksyuryel's status on Tuesday, 08-May-12 01:48:17 UTC
Using PostgreSQL, can a foreign key reference the table it appears in? Or is there some other way to do this? !coderpony #SQL
toksyuryel: The Pyramid tutorials could really do with some work. They don't spend much time introducing the concepts and explaining what you're doing at each step, they just give you a bunch of code to copy and paste with only an overall description of what it aims to do when they bother to describe it at all. The writing is also vague and uncertain, like it *means* to give a high-level introduction and then dive in but then it just moves on to the next topic instead of diving in. Here's a tip guys: if I'm reading the tutorial it's because I want to learn how to use your software, not because I'm still deciding whether or not I should use your software. At this point I really don't know much more about how to use it than I did before I went through the tutorials. Guess it's back to plan B then: read somebody else's Pyramid app and try to figure out how it works while cross-referencing the API docs. !coderpony !python
toksyuryel's status on Sunday, 06-May-12 21:01:49 UTC
The Pyramid tutorials could really do with some work. They don't spend much time introducing the concepts and explaining what you're doing at each step, they just give you a bunch of code to copy and paste with only an overall description of what it aims to do when they bother to describe it at all. The writing is also vague and uncertain, like it *means* to give a high-level introduction and then dive in but then it just moves on to the next topic instead of diving in. Here's a tip guys: if I'm reading the tutorial it's because I want to learn how to use your software, not because I'm still deciding whether or not I should use your software. At this point I really don't know much more about how to use it than I did before I went through the tutorials. Guess it's back to plan B then: read somebody else's Pyramid app and try to figure out how it works while cross-referencing the API docs. !coderpony !python
toksyuryel: Very slowly beginning to understand how decorators work. !python !coderpony
toksyuryel's status on Friday, 04-May-12 19:48:05 UTC
Very slowly beginning to understand how decorators work. !python !coderpony
toksyuryel: This is a wonderful read http://zedshaw.com/essays/programmer_stats.html !coderpony #NSFW
toksyuryel's status on Friday, 04-May-12 17:10:47 UTC
This is a wonderful read http://zedshaw.com/essays/programmer_stats.html !coderpony #NSFW
toksyuryel: "Welcome to Pyramid. Sorry for the convenience." !coderpony !python
toksyuryel's status on Friday, 04-May-12 15:31:36 UTC
"Welcome to Pyramid. Sorry for the convenience." !coderpony !python