Notices by Toksyuryel (toksyuryel) tagged coderpony

Toksyuryel Coder Ponies!

This is helpful http://blog.sanctum.geek.nz/vim-misconceptions/ !coderpony

Toksyuryel Coder Ponies!

So can someone maybe explain closures to me in as few buzzwords as possible? !coderpony

Toksyuryel Coder Ponies!

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 Spiral Knights Players , deadname , Toothpaste Pony! , Bit Shift

@minti @widget Come play !sk with me and @bitshift so we can have the whole #coderpony crew on at once :D

Toksyuryel Coder Ponies! , deadname , Bit Shift

Before I go to bed, I wanted to share this because it makes me happy. http://dpaste.com/749403/ @widget @bitshift !coderpony #SQL

Toksyuryel Coder Ponies! , deadname , Bit Shift

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 Coder Ponies! , deadname , Bit Shift

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 Coder Ponies!

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 Coder Ponies! , deadname , Bit Shift

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 Coder Ponies! , deadname , Bit Shift

Here's a comparison of uncached performance vs cached performance http://dpaste.com/747276/ @bitshift @widget !coderpony #SQL

Toksyuryel Coder Ponies! , deadname , Bit Shift

I'm pretty happy about this. http://dpaste.com/746779/ @widget @bitshift !coderpony #SQL

Toksyuryel Coder Ponies!

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 Coder Ponies! , Bit Shift

Today's lesson: arrays are evil. http://dpaste.com/745811/ @bitshift !coderpony #SQL

Toksyuryel Coder Ponies!

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 Coder Ponies!

Using PostgreSQL, can a foreign key reference the table it appears in? Or is there some other way to do this? !coderpony #SQL

Toksyuryel Python , Coder Ponies!

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 Python , Coder Ponies!

Very slowly beginning to understand how decorators work. !python !coderpony

Toksyuryel Coder Ponies!

This is a wonderful read http://zedshaw.com/essays/programmer_stats.html !coderpony #NSFW

Toksyuryel Python , Coder Ponies!

"Welcome to Pyramid. Sorry for the convenience." !coderpony !python