| 00:00.13 | *** join/#storm wallflower (n=wallflow@216.113.246.205) |
| 00:23.02 | *** join/#storm jml (n=jml@ppp121-44-213-76.lns1.hba1.internode.on.net) |
| 02:39.44 | *** join/#storm leifkb (n=leifkb@dsl82.brbovtma.sover.net) |
| 02:44.20 | *** join/#storm leifkb (n=leifkb@dsl82.brbovtma.sover.net) |
| 03:42.34 | *** join/#storm jml (n=jml@dsl-210-15-197-192-static.TAS.netspace.net.au) |
| 05:44.41 | *** join/#storm jml_ (n=jml@ppp121-44-213-76.lns1.hba1.internode.on.net) |
| 06:03.51 | *** join/#storm jukart (n=jukart@lsfw01.lovelysystems.com) |
| 07:32.53 | *** join/#storm dobee (n=dobeee@194.183.146.186) |
| 07:50.22 | *** join/#storm mcella (n=michele@ip-176-22.sn2.eutelia.it) |
| 09:09.56 | *** join/#storm Key_Gena8 (i=lok@gateway/tor/x-1b2578551decca64) |
| 10:41.50 | *** join/#storm rafael_ (n=rafael@p5089DB87.dip.t-dialin.net) |
| 11:54.41 | *** join/#storm jukart (n=jukart@lsfw01.lovelysystems.com) |
| 12:04.20 | *** join/#storm statik (n=emurphy@189.66.188.72.cfl.res.rr.com) |
| 12:21.13 | *** join/#storm niemeyer (n=niemeyer@200.103.134.216) |
| 12:29.48 | jamesh | hi niemeyer |
| 12:30.02 | niemeyer | jamesh: Hello James! |
| 12:31.14 | jamesh | niemeyer: I got the database disconnect branch mostly ready and pushed |
| 12:31.39 | jamesh | but the LP branch publisher seems to be having problems and the last few revisions aren't public yet |
| 12:31.50 | niemeyer | jamesh: Sweet! |
| 12:38.45 | jamesh | niemeyer: are you currently doing any retry handling with Storm in Landscape? |
| 12:39.23 | niemeyer | jamesh: Not yet.. |
| 12:39.42 | niemeyer | jamesh: Client => server communication have retries, but in a different level |
| 12:49.32 | *** join/#storm jml (n=jml@ppp121-44-213-76.lns1.hba1.internode.on.net) |
| 12:55.35 | niemeyer | jamesh: From the description you posted it looks like a nice approach |
| 12:57.55 | jamesh | niemeyer: I filed a bug against zope 3 about making it easier to mark exceptions as retryable. |
| 12:59.09 | jamesh | Jim proposed an alternative way to do it, but hopefully we'll be able to make zstorm automatically retry disconnections and other relevant exceptions |
| 13:05.00 | jamesh | niemeyer: I've just sent an up to date patch to the list, if you're interested in seeing the current code |
| 13:05.38 | *** join/#storm EnTeQuAk (n=EnTeQuAk@p57B9B8B6.dip0.t-ipconnect.de) |
| 13:06.47 | niemeyer | jamesh: Hmmm.. |
| 13:07.00 | niemeyer | jamesh: Doesn't Zope offer a Retry exception already? |
| 13:07.19 | jamesh | niemeyer: yes it does |
| 13:07.38 | niemeyer | jamesh: I wonder if injecting it as a base of DisconnectionError would be enough |
| 13:08.01 | jamesh | niemeyer: https://bugs.edge.launchpad.net/zope3/+bug/137905 |
| 13:08.07 | ubot3 | Malone bug 137905 in zope3 "Make it easier to raise retryable exceptions" [Undecided,Confirmed] |
| 13:08.52 | niemeyer | Except that I guess we'd have to form a diamond if we wanted to make DisconnectError inherit from any DBAPI exception as well |
| 13:09.41 | jamesh | as it currently stands you have two options: raise a Retry early, and get truncated exceptions on failed requests |
| 13:09.55 | jamesh | or check for each exception you want to retry in the publisher's handle_exception() method |
| 13:14.12 | *** join/#storm WebMaven (n=webmaven@63-253-185-227.ip.mcleodusa.net) |
| 13:14.39 | niemeyer | jamesh: Just looked at it.. makes sense, even though I think the marker approach is more explicit and consequently cleaner |
| 13:15.13 | niemeyer | WebMaven: Heya |
| 13:17.40 | jamesh | niemeyer: yeah. I need to test the view approach to see if it actually solves the problem |
| 13:17.53 | jamesh | if it doesn't, we might get the marker interface |
| 13:18.55 | WebMaven | niemeyer: yo |
| 13:18.56 | niemeyer | jamesh: It most probably may solve, but certainly will require tweaks in handleException |
| 13:20.59 | jamesh | niemeyer: I suspect it'd cause problems if you also want to display an error to the user |
| 13:21.09 | niemeyer | jamesh: Looking at the method, at least the error will get logged when the Retry is raised by the view, while it's not in other situations |
| 13:21.47 | jamesh | niemeyer: usually I'd only want the exception logged if I exhaust the retries |
| 13:21.54 | niemeyer | jamesh: Agreed |
| 13:23.02 | niemeyer | jamesh: For displaying the error, I think the view would have to be aware of the counting logic |
| 13:23.37 | jamesh | I suppose it could check request.supportsRetry() to decide whether to render an error page or raise Retry() |
| 13:24.02 | jamesh | but this gets a bit complicated |
| 13:24.11 | jamesh | and ties rendering of the error page to the retry behaviour |
| 13:25.59 | niemeyer | Right.. just making the view decide to Retry a request already sounds like crossing domain boundaries incorrectly |
| 13:37.25 | *** join/#storm WebMaven (n=webmaven@63-253-185-227.ip.mcleodusa.net) |
| 13:46.04 | *** join/#storm statik (n=emurphy@189.66.188.72.cfl.res.rr.com) |
| 14:14.16 | *** join/#storm WebMaven (n=webmaven@63-253-185-227.ip.mcleodusa.net) |
| 14:15.07 | *** join/#storm mcella (n=michele@ip-176-22.sn2.eutelia.it) |
| 14:31.27 | *** join/#storm brosner (n=brian@63.150.173.39) |
| 14:35.35 | *** join/#storm oubiwann (n=oubiwann@209-181-153-103.omah.qwest.net) |
| 15:32.48 | *** join/#storm michelp (n=michelp@69-30-72-119.dq1sf.easystreet.com) |
| 15:48.57 | *** join/#storm statik (n=emurphy@189.66.188.72.cfl.res.rr.com) |
| 16:20.48 | *** join/#storm Key_Gena8 (i=lok@gateway/tor/x-cfcc803f7d9ec454) |
| 16:28.32 | EnTeQuAk | ehm, If I implement a Reference. Are there any attributes in the "referenced" columns showing that they're part of a reference? |
| 16:30.40 | radix | huh |
| 16:30.52 | radix | EnTeQuAk: I don't understand your question |
| 16:32.25 | EnTeQuAk | I can mark a column as a reference to other columns. |
| 16:33.14 | jamesh | EnTeQuAk: maybe it would help if you tried to describe what you want to do at a higher level |
| 16:33.27 | EnTeQuAk | yepp, still in progress ;) |
| 16:36.26 | EnTeQuAk | please take a look at http://paste.pocoo.org/show/3992/ |
| 16:36.59 | EnTeQuAk | If I have the property object of `People.school_id` |
| 16:37.33 | EnTeQuAk | are there any attributes that shows that People.school_id is referenced to School.id ? |
| 16:40.12 | niemeyer | EnTeQuAk: Ok.. so what do you want to do? |
| 16:40.31 | niemeyer | EnTeQuAk: The reference you explicitly declared of course shows that it's a reference |
| 16:41.02 | EnTeQuAk | niemeyer, I'm still working on the automatic schema creation and for now I'm just watching at the PropertyColumn related attributes. |
| 16:41.18 | niemeyer | EnTeQuAk: Ah, that, ok :) |
| 16:41.31 | niemeyer | EnTeQuAk: No, there's nothing in school_id that shows the reference |
| 16:41.55 | EnTeQuAk | damn... Then I have to go the longer way :D |
| 16:41.59 | niemeyer | EnTeQuAk: The reference is the only thing that says that, well, a reference exists (that sounds badly circular :) |
| 16:42.42 | EnTeQuAk | ahh, I understand. Then I have an idea how to implement the Reference things. |
| 16:43.32 | EnTeQuAk | ehm, by the way: What's about Proxies. What are they exactly, should I handle them in the CREATE TABLE - Code? |
| 16:45.15 | niemeyer | EnTeQuAk: Proxies are a way to use an attribute of a referenced object as if it were a local one |
| 16:45.26 | niemeyer | EnTeQuAk: I don't think it makes sense in that context |
| 16:46.22 | EnTeQuAk | hmm, that means: (in my example code) --- that I can use School.id as a key, defined in the People class? |
| 16:46.56 | niemeyer | No.. Proxies are something which work on top of everything else |
| 16:47.09 | EnTeQuAk | ahh, ok :D |
| 16:47.11 | niemeyer | They are not a replacement for any of the concepts already in your toolbox |
| 16:47.49 | niemeyer | EnTeQuAk: They are just there for comfort.. |
| 16:48.12 | *** join/#storm jukart (n=jukart@85-124-221-45.static.xdsl-line.inode.at) |
| 16:48.27 | EnTeQuAk | good, then the're not important for the automatic table creation |
| 16:49.08 | niemeyer | Right |
| 16:50.52 | EnTeQuAk | btw: I'll also implement a `max_length` attribute for some Properties (e.g Int and Unicode/RawStr, maybe it also makes sense for List's) |
| 16:59.40 | niemeyer | max_length for ints? |
| 17:00.45 | EnTeQuAk | I just remembered that there are `smallint`, `int` and some other kinds of integer types in SQL defined |
| 17:02.07 | niemeyer | EnTeQuAk: Right.. max_length looks like an inappropriate name for the concept |
| 17:04.09 | EnTeQuAk | maybe, I'm searching for another one ;) |
| 17:15.42 | *** part/#storm mcella (n=michele@ip-176-22.sn2.eutelia.it) |
| 17:24.08 | radix | EnTeQuAk: "size" is probably a better word than "length" |
| 17:47.32 | EnTeQuAk | yey, thanks radix :D |
| 17:55.17 | *** join/#storm dobee (n=dobeee@81-223-53-162.dornbirn.xdsl-line.inode.at) |
| 18:55.19 | *** join/#storm dobee (n=dobeee@81-223-53-162.dornbirn.xdsl-line.inode.at) |
| 19:22.28 | *** join/#storm jukart (n=jukart@85-124-221-45.static.xdsl-line.inode.at) |
| 19:26.30 | *** join/#storm jukart_ (n=jukart@85-124-221-45.static.xdsl-line.inode.at) |
| 19:27.27 | *** join/#storm jukart (n=jukart@85-124-221-45.static.xdsl-line.inode.at) |
| 19:39.09 | *** join/#storm jukart_ (n=jukart@85-124-221-45.static.xdsl-line.inode.at) |
| 19:50.18 | *** join/#storm dobee (n=dobeee@81-223-53-162.dornbirn.xdsl-line.inode.at) |
| 20:40.49 | *** join/#storm WebMaven (n=webmaven@63-253-185-227.ip.mcleodusa.net) |
| 21:09.21 | *** join/#storm michelp (n=michelp@69-30-72-119.dq1sf.easystreet.com) |
| 22:40.07 | *** join/#storm jukart (n=jukart@85-124-221-45.static.xdsl-line.inode.at) |
| 23:15.23 | *** join/#storm brosner (n=brian@63.150.173.39) |