Logs for jdev

Show join/part/nick changes:

[00:18:44] * marseille left the chat.
[00:43:55] * alkino left the chat.
[01:02:14] * luca tagliaferri left the chat.
[01:02:31] * marseille joined the chat.
[01:06:26] * evilotto left the chat.
[02:12:11] * scippio left the chat.
[02:13:52] * marseille left the chat.
[03:21:57] * darkrain joined the chat.
[06:38:39] * nabatt joined the chat.
[06:39:55] * thkoch2001 joined the chat.
[08:07:24] * luca tagliaferri joined the chat.
[08:08:29] * harrykar left the chat.
[08:13:35] * harrykar joined the chat.
[08:14:19] * harrykar left the chat.
[08:15:21] * harrykar joined the chat.
[08:50:52] * petermount joined the chat.
[08:54:30] * Asterix joined the chat.
[09:13:24] * guus joined the chat.
[09:31:30] * ABV joined the chat.
[09:31:45] * ABV left the chat.
[09:32:24] * petermount left the chat.
[09:39:09] * harrykar left the chat.
[09:42:01] * guus left the chat.
[09:43:12] * xnyhps left the chat.
[09:49:22] * xnyhps joined the chat.
[09:51:05] * dwd left the chat.
[09:57:50] * guus joined the chat.
[09:58:45] * xnyhps left the chat.
[10:01:51] * xnyhps joined the chat.
[10:02:24] * xnyhps left the chat.
[10:02:33] * xnyhps joined the chat.
[10:07:23] * dwd joined the chat.
[10:24:29] * Kev joined the chat.
[10:30:34] * marseille joined the chat.
[10:38:10] * ralphm joined the chat.
[10:38:15] * alkino joined the chat.
[10:39:23] <ralphm> Hmm, the xmpp.org muc logs give 500s
[10:39:23] * dwd left the chat.
[10:40:10] * ralphm_ joined the chat.
[10:40:48] <ralphm> http://logs.xmpp.org/
[10:41:35] * Asterix left the chat.
[10:47:15] * Tobias joined the chat.
[10:53:31] * ralphm_ left the chat.
[12:06:23] * Zash joined the chat.
[12:16:20] * deryni left the chat.
[12:33:11] * ralphm left the chat.
[12:34:16] * marseille left the chat.
[12:35:40] * marseille joined the chat.
[12:37:24] * harrykar joined the chat.
[12:38:03] * harrykar left the chat.
[12:41:05] * harrykar joined the chat.
[12:55:29] * marseille left the chat.
[12:58:15] * marseille joined the chat.
[13:07:37] * deryni joined the chat.
[13:14:22] * Link Mauve left the chat.
[13:15:26] * Link Mauve joined the chat.
[13:25:43] * akuckartz joined the chat.
[13:37:36] * scippio joined the chat.
[13:46:43] * Xificurk joined the chat.
[13:53:06] * akuckartz left the chat.
[13:54:40] * Florob joined the chat.
[14:28:40] * deryni left the chat.
[14:47:19] * alkino left the chat.
[15:07:04] * nabatt left the chat.
[15:22:49] <Zash> Hm, did the DST change or something make planet.j.o upset?
[15:45:02] * darkrain_ joined the chat.
[15:45:47] <guus> We're trying to adapt XEP-0059 (Result Set Management), but we run into issues when we try to have the result set backed by a relational database. Our primary issue is that we can't find a way in SQL to identify the 'next few' results in a larger result set, based on a unique identifier (which is what the spec appears to favor).
[15:47:06] <guus> They most obvious way to achieve this, would result in moving the entire database-table in memory (to find the appropriate results for a particular page), but that has obvious performance penalties
[15:47:09] <guus> Does anyone have experience mapping RSM functionality to a relational database?
[15:47:40] <Zash> Doesn't it map somewhat cleanly to LIMIT ?
[15:48:13] <Zash> Hrm
[15:48:39] <guus> getting result sets in smaller chucnks isn't much of a problem (although 'LIMIT' is proprietary to MySQL, I believe)
[15:49:29] <Zash> Oh, didn't know that.
[15:49:39] <guus> We can't find a way to express this in SQL: "I want the next x rows from table y after the row identified by <unique_key> when table y is sorted by z.
[15:50:47] <guus> or, alternatively (but equally elusive to us): I want the index in the total result set of the result identified by <unique_key> from table y when sorted by z."
[15:50:56] <guus> sorted by / ordered by
[15:51:46] <guus> we can, of course, simply iterate over all results until I hit the correct one, but that's a serious performance bottleneck for non-trivial table sizes.
[15:52:24] <guus> and worse: It's hard to do that in SQL, meaning that I'd have to do it in application code.
[15:53:35] <guus> the 'before' and 'after' instructions in RSM appear to favor this kind of behavior (things get a lot easier from a SQL perspective if you use 'index')
[15:54:51] <guus> but as the spec is a draft standard, and I assume that data is typically persisted in a relational database, I'd expect these kind of issues to be discussed before. I've browsed the standards mailinglist archive, but nothing popped up though.
[16:00:52] * Tobias left the chat.
[16:09:06] * thkoch2001 left the chat.
[16:10:53] * Florob left the chat.
[16:10:54] * Asterix joined the chat.
[16:10:54] * Florob joined the chat.
[16:38:56] * alkino joined the chat.
[16:45:04] * guus left the chat.
[16:51:14] * evilotto joined the chat.
[17:12:53] * Tobias joined the chat.
[17:37:20] * Lance joined the chat.
[17:37:20] * Lance left the chat.
[17:39:08] * Lance joined the chat.
[17:42:39] * scippio left the chat.
[17:48:29] * nielsvh joined the chat.
[18:01:29] * nielsvh left the chat.
[18:53:02] * luca tagliaferri left the chat.
[19:13:31] * scippio joined the chat.
[19:47:05] * Treebilou left the chat.
[19:50:36] * luca tagliaferri joined the chat.
[19:59:01] * Florob left the chat.
[20:00:24] * deryni joined the chat.
[20:54:12] * marseille left the chat.
[20:55:48] * mathieui joined the chat.
[20:57:17] * marseille joined the chat.
[21:26:36] * guus joined the chat.
[22:01:11] * Asterix left the chat.
[22:11:12] * marseille left the chat.
[22:13:47] * marseille joined the chat.
[22:30:06] * guus left the chat.
[22:31:01] * scippio left the chat.
[22:31:07] * scippio joined the chat.
[22:51:19] * luca tagliaferri left the chat.
[22:57:18] * marseille left the chat.
[22:57:36] * marseille joined the chat.
[23:00:23] * marseille left the chat.
[23:02:20] * marseille joined the chat.
[23:21:17] * evilotto left the chat.
[23:31:20] * marseille left the chat.
[23:32:56] * marseille joined the chat.