| 00:00.15 | *** join/#storm wallflower (n=wallflow@ip-205-246-113-216.pool.grokthis.net) |
| 00:04.36 | weatherman_ | storm/database-trace-hook r183 committed by radix@twistedmatrix.com |
| 00:04.37 | weatherman_ | Merge trunk into database-trace-hook |
| 04:26.42 | *** join/#storm Key_Gena (i=lok@gateway/tor/x-2d8a9aa7ef4fe1ec) |
| 06:38.43 | *** join/#storm dobee (n=dobeee@194.183.146.186) |
| 06:44.30 | *** join/#storm jukart (n=jukart@194.183.146.181) |
| 07:39.19 | *** join/#storm bozzo (n=bozzo@BSN-210-221-23.dial-up.dsl.siol.net) |
| 08:22.56 | *** join/#storm Fujitsu (n=fujitsu@ubuntu/member/fujitsu) |
| 09:23.23 | *** join/#storm mcella (n=michele@ip-171-30.sn3.eutelia.it) |
| 11:21.58 | *** join/#storm bozzo (n=bozzo@BSN-77-199-65.dial-up.dsl.siol.net) |
| 11:23.15 | *** join/#storm bozzo (n=bozzo@BSN-77-199-65.dial-up.dsl.siol.net) |
| 12:11.48 | *** join/#storm niemeyer (n=niemeyer@200-138-134-89.ctame705.dsl.brasiltelecom.net.br) |
| 13:03.47 | weatherman_ | storm/trunk r192 committed by gustavo@niemeyer.net |
| 13:03.47 | weatherman_ | Added TimeDelta to locals. |
| 13:08.33 | weatherman_ | storm/trunk r192 committed by gustavo@niemeyer.net |
| 13:08.33 | weatherman_ | Added TimeDelta to locals. [trivial] |
| 13:10.30 | *** join/#storm mcella_ (n=michele@ip-171-30.sn3.eutelia.it) |
| 13:59.31 | *** join/#storm Zenom (n=Zenom@unaffiliated/aj1973) |
| 15:06.00 | jkakar | niemeyer: Given the awesomeness that insert-returning brought in yesterday, do you think we should prepare a release? |
| 15:07.08 | niemeyer | jkakar: I think we should do one shortly |
| 15:07.20 | niemeyer | jkakar: There are a few things I'd like to integrate before the release |
| 15:07.49 | niemeyer | jkakar: Like support for timedelta in sqlite and reconnection for mysql |
| 15:08.22 | jkakar | niemeyer: Ah, okay, cool. |
| 15:11.19 | *** join/#storm dobee (n=dobeee@81-223-53-162.dornbirn.xdsl-line.inode.at) |
| 16:13.51 | *** join/#storm EnTeQuAk (n=EnTeQuAk@dslb-088-074-037-063.pools.arcor-ip.net) |
| 17:13.26 | *** join/#storm [algo] (n=ilia@algo.dialup.corbina.ru) |
| 17:13.29 | [algo] | hello |
| 17:13.38 | [algo] | I'm new to Storm |
| 17:14.21 | [algo] | why should I take it instead of django/SQL Alchemy ? |
| 17:14.43 | radix | Hi. |
| 17:15.15 | [algo] | hi |
| 17:16.11 | radix | because Storm is nice and simple. |
| 17:24.12 | niemeyer | Because it performs better, because it's cool, because it's awesome while the others are not, or like my friend Jeff Johnson would say, just because. ;-) |
| 17:25.02 | [algo] | eeck |
| 17:26.41 | niemeyer | [algo]: More seriously, there's a list of features in the web site, and the tutorial should give you an idea about how it works |
| 17:26.59 | niemeyer | [algo]: You then have to decide if that's what you're looking for or not |
| 17:27.07 | niemeyer | [algo]: We can help you with specific questions if you have any |
| 17:27.12 | [algo] | fine thanks |
| 17:59.23 | *** join/#storm jml_ (n=jml@70.91.133.153) |
| 18:16.39 | Zenom | debating on switching to hg or bzr for vcs instead of svn |
| 18:16.58 | jkakar | ++bzr! |
| 18:17.22 | jkakar | Seriously, I haven't actually used hg, so I can't comment on it. I use bzr for all my projects and love it. |
| 18:17.37 | Zenom | our thing is we get tired of going "are you in such and such file?" |
| 18:17.47 | Zenom | i am just curious about how merges actually happen |
| 18:17.56 | Zenom | and how we can manage it with a group of only 3 people |
| 18:18.04 | jkakar | Zenom: One of the things that changes is that you end up doing things in branches. |
| 18:18.19 | jkakar | Zenom: So, in our case for example, we have a trunk/ branch that we all merge into when branches are ready. |
| 18:18.42 | Zenom | yeah we typically work on the same stuff |
| 18:18.42 | jkakar | Zenom: As an aside, we have a requirement that all branches get 2 reviews before being merged to trunk. But that has nothing to do with the VCS. |
| 18:18.48 | Zenom | ie., like in the db module or whatever |
| 18:19.18 | jkakar | Zenom: On the same feature, or just on the same components? |
| 18:19.19 | Zenom | sometimes on the same feature |
| 18:19.21 | Zenom | for instance right now we are writing a blogging app |
| 18:19.31 | Zenom | and we kinda go back and forth based on tickets that are open for bugs |
| 18:19.39 | jkakar | So, in that case you're closely collaborating on whether programmer A has committed a file programmer B needs? |
| 18:19.46 | Zenom | sometimes yeah |
| 18:20.32 | jkakar | In that case, bzr supports the svn centralized model ('bzr checkout' instead of 'bzr branch'). It would be interesting to hop into #bzr and discuss your use cases with the guys there. It's a very flexible tool. |
| 18:21.14 | Zenom | thanks might do that |
| 18:22.22 | Zenom | so from my reading it looks like you have a local branch |
| 18:22.28 | Zenom | then you just push to a central repo |
| 18:23.06 | jkakar | You can do that, yes. |
| 18:23.39 | jkakar | You can also have a central branch that you have a "checkout" of. Commits to your local copy have to succeed on the remote branch before they go through. Similar to the svn model. |
| 18:24.47 | jkakar | Zenom: John Arbash Meinl, on of the Bazaar developer's recently wrote a comparison of svn and bzr that might be insightful: http://jam-bazaar.blogspot.com/2007/10/bazaar-vs-subversion.html |
| 18:25.25 | jkakar | Zenom: There are also tools like bzr-svn that might be useful during the transition/checking it out phase. |
| 18:30.05 | Zenom | i think part of the things I am scared about |
| 18:30.16 | Zenom | is all of us edit a single file and me not being bzr, hg friendly enough |
| 18:30.22 | Zenom | that the whole thing gets borked lol |
| 19:16.06 | niemeyer | It's *UNBELIEVABLE* how people have no idea about the meaning of a transaction |
| 19:16.15 | niemeyer | MySQLdb is totally screwed up |
| 19:16.40 | niemeyer | It does automatic reconnection by defaut |
| 19:16.41 | niemeyer | default |
| 19:16.47 | niemeyer | So far so good.. |
| 19:17.29 | niemeyer | But the "detail" is that once it reconnects, it doesn't tell you that your on going transaction was actually rolled back |
| 19:17.36 | niemeyer | Not only that, but it will put you in *AUTOCOMMIT* mode |
| 19:17.42 | niemeyer | Man.. |
| 19:18.07 | niemeyer | All of that without a single notice to the application |
| 19:39.58 | niemeyer | To be fair, it's not a fault of MySQLdb.. MySQL itself implemented the reconnect behavior by default during 5.0 and 5.0.3. |
| 19:40.09 | niemeyer | They disabled it after 5.0.3 (probably understood how bad it was) |
| 19:40.30 | niemeyer | and Debian (and Ubuntu by consequence) have a patch reenabling it by default.. |
| 19:40.37 | niemeyer | Even in 5.0.3+ |
| 19:40.50 | niemeyer | So it's not a problem of MySQLdb per-se |
| 19:46.40 | radix | :| |
| 19:48.24 | niemeyer | Aha, found a workaround |
| 20:30.12 | weatherman_ | storm/trunk r193 committed by gustavo@niemeyer.net |
| 20:30.12 | weatherman_ | Updating NEWS file. |
| 20:42.07 | niemeyer | michelp: I'm getting this error when running the schema upgrades of client_uptime_sux: |
| 20:42.09 | niemeyer | <PROTECTED> |
| 20:42.10 | niemeyer | psycopg2.ProgrammingError: relation "client_uptime_component" does not exist |
| 20:42.35 | niemeyer | michelp: Actually |
| 20:42.47 | niemeyer | michelp: I think it's not in the patch |
| 20:42.52 | radix | mischan :) |
| 20:43.02 | niemeyer | DUH |
| 20:46.40 | pyCube | i dunno.. not a db expert here, but mysql alays put me off for some reason |
| 20:52.00 | weatherman_ | storm/mysql-reconnection r194 committed by gustavo@niemeyer.net |
| 20:52.00 | weatherman_ | Implemented reconnection support in MySQL backend. |
| 20:57.03 | niemeyer | radix, jkakar: ^^^ That's up for review on #94986 |
| 20:57.11 | radix | cool! |
| 20:57.13 | niemeyer | It's a very small change |
| 20:58.12 | jkakar | Yay |
| 21:04.25 | pyCube | niemeyer: thanks again for tackling the postgrsql schema thing.. very useful here :-) |
| 21:52.41 | niemeyer | pyCube: You're welcome! |
| 21:52.50 | niemeyer | pyCube: My I ask where you're using Storm? |
| 21:53.18 | pyCube | where? |
| 21:56.13 | niemeyer | pyCube: Which project |
| 21:56.43 | niemeyer | pyCube: Sorry, bad english "where are you" |
| 22:22.10 | pyCube | heh.. well, i am in arizona atm.. moving to northern california in a couple weeks |
| 22:22.20 | pyCube | oh |
| 22:22.22 | pyCube | sheesh |
| 22:24.56 | pyCube | using storm on some projects that piggy back off of the school/curriculum app i built using twisted/nevow and twisteds adbapi |
| 22:25.49 | pyCube | really pretty much reimplementing the thing, but first as an xmlrpc api |
| 22:26.57 | pyCube | so with storm i am partly mapping to existing tables and such, but also building new apps and tables |
| 22:29.37 | pyCube | but, all that will change in a couple weeks |
| 22:29.39 | pyCube | hehe |
| 22:29.54 | pyCube | and hopefully i'll be using storm a lot in my new job |
| 22:38.01 | pyCube | i really like how much db design/usage opens up when I approach it all object oriented like.. |
| 22:38.26 | pyCube | writing sql is a bitch... period |
| 22:38.28 | pyCube | hehe |
| 22:38.31 | jkakar | Heh |
| 22:39.24 | pyCube | i just feel like the db structure is much more sound and useful when i attack it from the get go as class, instance, property, etc |
| 22:39.33 | pyCube | the ones i make anyway.. hehe |
| 22:40.27 | pyCube | helps me exploit the power of a relational db |
| 22:42.23 | pyCube | i have been wearing a lot of hats at work for the past 4 years or so.. having time to sit and become mr sql guru just never happened.. hehe |
| 22:44.02 | pyCube | the nice thing about storm is that it just lays right over whatever db design you have, rather than imposing all sorts of crap on you design wise |
| 22:44.36 | pyCube | ..and, unlike some other similar things, it doesnt end up being more of a bitch than just dealing with sql |
| 22:44.38 | pyCube | :-p |
| 22:45.52 | pyCube | sql + getting you results in some dumb list or slightly less dumb dict |
| 22:46.46 | pyCube | anyway... |
| 22:49.36 | pyCube | i dunno.. sql is kinda like css, inherently trial and errory.. for me that is |
| 22:50.34 | pyCube | lead to a lot of "ok, WTF!? this *should* be working..." |
| 22:50.46 | pyCube | hehe |
| 22:51.00 | aa_ | css is a bit more forgiving when you get things wrong |
| 22:51.08 | pyCube | hehe |
| 22:51.09 | pyCube | yeah |
| 22:51.38 | pyCube | a misplaced div is less painful than a couple million extra rows from a query |
| 23:21.30 | *** join/#storm pyCube (n=jmayfiel@ip72-208-138-205.ph.ph.cox.net) |