| 00:23.40 | *** join/#storm niemeyer_ (~niemeyer@189.27.144.191.dynamic.adsl.gvt.net.br) |
| 00:43.19 | *** join/#storm veloutin (~vvinet@2001:470:8829:1000:227:eff:fe25:ee64) |
| 02:22.38 | *** join/#storm niemeyer_ (~niemeyer@189.27.144.191.dynamic.adsl.gvt.net.br) |
| 05:31.41 | *** join/#storm zmijunkie (~sascha@83.135.3.203) |
| 06:40.53 | *** join/#storm stub (~stub@canonical/launchpad/stub) |
| 07:15.27 | *** join/#storm vokoda (~user@unaffiliated/vokoda) |
| 07:25.52 | *** join/#storm esteve (~quassel@cli-5b7ee22f.bcn.adamo.es) |
| 08:06.37 | *** join/#storm bigjools (~quassel@canonical/launchpad/bigjools) |
| 08:37.56 | *** join/#storm danilos (~danilo@canonical/launchpad/danilos) |
| 08:47.25 | *** join/#storm wallyworld (~quassel@27-33-46-253.static.tpgi.com.au) |
| 10:10.28 | *** join/#storm stub (~stub@canonical/launchpad/stub) |
| 13:12.22 | *** join/#storm fcorrea (~fcorrea@186.252.58.100) |
| 15:38.33 | *** join/#storm fcorrea (~fcorrea@189.121.209.94) |
| 16:14.01 | *** join/#storm jkakar (~jkakar@131.Red-88-5-210.dynamicIP.rima-tde.net) |
| 16:17.02 | *** join/#storm keppla (~keppla@p4FD45FD5.dip.t-dialin.net) |
| 16:30.56 | *** join/#storm keppla (~keppla@p4FD45FD5.dip.t-dialin.net) |
| 16:33.38 | *** join/#storm webmaven (~webmaven@136.sub-174-253-242.myvzw.com) |
| 16:39.22 | *** join/#storm keppla (~keppla@p4FD45FD5.dip.t-dialin.net) |
| 16:43.21 | *** join/#storm jkakar (~jkakar@131.Red-88-5-210.dynamicIP.rima-tde.net) |
| 17:02.42 | vokoda | not sure if this place is active.. but I'm trying to figure out how storm's django integration works. storm.django.middleware.ZopeTransactionMiddleware "configures the Zope transaction manager to run a transaction over each Django request" what does this mean exactly? |
| 17:03.09 | vokoda | does it effectively mean doing a store.commit() on all stores at the end of each request? |
| 17:03.31 | jkakar | vokoda: Hi! |
| 17:03.37 | jkakar | vokoda: We're active here. :) |
| 17:03.41 | vokoda | I don't have any familiarity with zope apart from zope.interface |
| 17:03.45 | vokoda | hi jkakar |
| 17:03.46 | jkakar | vokoda: That statement you quoted is very confusing. :) |
| 17:04.14 | jkakar | vokoda: Basically, we have a Zope plugin that sets up stores with the 'transaction' module and works correctly when threads are used. |
| 17:04.55 | jkakar | vokoda: The Django integration reuses the Zope plugin, because it can basically. |
| 17:05.13 | vokoda | ahh ok, I see |
| 17:05.53 | vokoda | that makes sense I think, thanks jkakar |
| 17:06.22 | jkakar | vokoda: Cool. |
| 17:07.31 | jkakar | vokoda: Basically, when you have it registered correctly you can call storm.django.stores.get_store to get a store for a named database. Like get_store("main"), for example. |
| 17:07.47 | jkakar | vokoda: If everything goes well with the request, the store will be committed automatically and your changes will be persisted. |
| 17:08.02 | jkakar | vokoda: If an exception is raised the stores will be rolled back automatically. |
| 17:09.06 | jkakar | vokoda: Use the 'transaction' package to manage the transaction (since the Zope plugin integrates with it): import transaction; transaction.commit(); |
| 17:10.22 | vokoda | jkakar: right, so I should use transaction.commit() in addition to or instead of store.commit()? |
| 17:10.54 | jkakar | vokoda: Instead of. |
| 17:11.03 | jkakar | vokoda: If you look at the transaction module you'll see that you can do some cool things... |
| 17:11.31 | jkakar | vokoda: For example, you can register functions to call when a transaction succeeds. This is very useful for queuing emails to send. They only get sent if the transaction succeeds and don't if it fails. |
| 17:14.44 | vokoda | oh right, yeah that is cool. i'll have to read about transaction. |
| 17:14.53 | vokoda | i'm about the grab dinner, thanks for explaining that |
| 17:15.00 | vokoda | i've been really impressed by storm so far |
| 17:15.24 | jkakar | vokoda: Cool! :) |
| 17:23.57 | *** join/#storm wallyworld_ (~quassel@27-33-46-253.static.tpgi.com.au) |
| 17:46.14 | *** join/#storm zmijunkie (~sascha@i59F5D8F9.versanet.de) |
| 18:05.36 | *** join/#storm bigdog (~scmikes@72-197-8-8-arpa.cust.cincinnaticomm.net) |
| 19:37.39 | *** join/#storm webmaven (~webmaven@64.134.238.86) |
| 21:18.30 | vokoda | jkakar: is there anything I should know about using Storm and Django ORM at the same time? ZopeTransactionMiddleware autocommits the Storm transaction after processing the response, as you explained. but it seems to interfere with Django ORM's autocommit? I've only been able to commit a Django transaction by importing django.db.transaction and manually transaction.commit() |
| 21:20.49 | vokoda | I thought zope.transaction was being used to handle both the storm and django transaction, but I suppose not |
| 21:53.16 | vokoda | aha, I think I've figured it out. nevermind. |
| 23:18.22 | *** join/#storm wallyworld_ (~quassel@27-33-46-253.static.tpgi.com.au) |