Notices by Toksyuryel (toksyuryel) tagged coderpony

  1. This is helpful !coderpony

    Wednesday, 01-Aug-12 15:09:40 UTC from web
  2. So can someone maybe explain closures to me in as few buzzwords as possible? !coderpony

    Tuesday, 31-Jul-12 14:46:03 UTC from web
  3. Another great article from Eevee (as usual, lots of # language here) !coderpony

    Tuesday, 31-Jul-12 13:43:22 UTC from web
  4. @minti @widget Come play !sk with me and @bitshift so we can have the whole # crew on at once :D

    Monday, 23-Jul-12 20:06:20 UTC from web in context
  5. Before I go to bed, I wanted to share this because it makes me happy. @widget @bitshift !coderpony #

    Thursday, 17-May-12 16:31:19 UTC from web
  6. @aeniug2 You should join !coderpony

    Wednesday, 16-May-12 03:21:49 UTC from web in context
  7. 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. @bitshift @widget !coderpony #

    Monday, 14-May-12 09:32:33 UTC from web
  8. 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. @bitshift @widget !coderpony #

    Monday, 14-May-12 09:10:37 UTC from web
  9. 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: !coderpony #

    Monday, 14-May-12 08:23:58 UTC from web in context
  10. 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? @bitshift @widget !coderpony #

    Sunday, 13-May-12 01:13:01 UTC from web in context
  11. Here's a comparison of uncached performance vs cached performance @bitshift @widget !coderpony #

    Saturday, 12-May-12 20:37:27 UTC from web in context
  12. I'm pretty happy about this. @widget @bitshift !coderpony #

    Friday, 11-May-12 19:14:58 UTC from web
  13. 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 #

    Thursday, 10-May-12 00:42:11 UTC from web
  14. Today's lesson: arrays are evil. @bitshift !coderpony #

    Thursday, 10-May-12 00:31:17 UTC from web
  15. @bitshift I dunno, I designed half of it while half asleep anyway. Here it is anyway for your perusal (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 #

    Wednesday, 09-May-12 05:34:44 UTC from web in context
  16. @bitshift So how'd I do? :) !coderpony #

    Wednesday, 09-May-12 00:47:20 UTC from web in context
  17. @toksyuryel @bitshift I realized I forgot some conditionals in one of the stubbed functions, here's a fixed version of that !coderpony #

    Tuesday, 08-May-12 23:10:58 UTC from web in context
  18. @bitshift I have stubbed out several functions and created the triggers to demonstrate how I plan to constrain the arrays !coderpony #

    Tuesday, 08-May-12 23:05:16 UTC from web in context
  19. @bitshift Let's see how horribly I botched this one up !coderpony #

    Tuesday, 08-May-12 22:09:18 UTC from web in context
  20. @bitshift here's what it looks like now !coderpony #

    Tuesday, 08-May-12 20:50:47 UTC from web in context
  21. @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! !coderpony #

    Tuesday, 08-May-12 20:34:16 UTC from web in context
  22. 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 #

    Tuesday, 08-May-12 20:19:16 UTC from web in context
  23. Using PostgreSQL, can a foreign key reference the table it appears in? Or is there some other way to do this? !coderpony #

    Tuesday, 08-May-12 01:48:17 UTC from web in context
  24. 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

    Sunday, 06-May-12 21:01:49 UTC from web in context
  25. Very slowly beginning to understand how decorators work. !python !coderpony

    Friday, 04-May-12 19:48:05 UTC from web
  26. This is a wonderful read !coderpony #

    Friday, 04-May-12 17:10:47 UTC from web
  27. "Welcome to Pyramid. Sorry for the convenience." !coderpony !python

    Friday, 04-May-12 15:31:36 UTC from web