| 01:46.55 | *** join/#storm stub (~stub@ppp-58-8-12-61.revip2.asianet.co.th) |
| 01:46.55 | *** join/#storm stub (~stub@canonical/launchpad/stub) |
| 02:43.24 | *** join/#storm sidnei (~sidnei@200-203-115-55.cslce701.dsl.brasiltelecom.net.br) |
| 03:55.20 | *** join/#storm wallyworld (~quassel@27-33-46-253.static.tpgi.com.au) |
| 07:02.57 | *** join/#storm elmom_ (~elmom@hoasnet-fe29dd00-137.dhcp.inet.fi) |
| 07:42.02 | *** join/#storm bac (~bac@cpe-024-163-113-206.nc.res.rr.com) |
| 07:42.13 | *** join/#storm bac (~bac@canonical/launchpad/bac) |
| 08:01.00 | *** join/#storm bigjools (~quassel@82-71-93-254.dsl.in-addr.zen.co.uk) |
| 08:01.00 | *** join/#storm bigjools (~quassel@canonical/launchpad/bigjools) |
| 08:10.46 | *** join/#storm elmom_ (~elmom@vallila-gw.hupnet.helsinki.fi) |
| 09:07.38 | *** join/#storm keppla (~keppla@i577B219F.versanet.de) |
| 09:10.39 | *** join/#storm elmom_ (~elmom@vallila-gw.hupnet.helsinki.fi) |
| 09:42.01 | *** join/#storm zmijunkie (~sascha@i59F5E0DF.versanet.de) |
| 12:02.40 | *** join/#storm shaunm (~shaunm@74.83.18.167) |
| 12:25.51 | *** join/#storm fcorrea (~fcorrea@187.3.31.9) |
| 12:43.06 | *** join/#storm jukart (lovely@81.189.156.94) |
| 13:16.34 | *** join/#storm keppla1 (~keppla@i577B3C57.versanet.de) |
| 13:27.49 | *** join/#storm mgedmin (~mg@Maemo/community/contributor/mgedmin) |
| 13:29.17 | mgedmin | I would like to cache some SQL queries in a zope app |
| 13:29.18 | mgedmin | I assume that sticking storm's objects in a global dictionary would be a bad idea |
| 13:29.33 | mgedmin | each object is associated with a session, and each session is private to a thread |
| 13:29.49 | mgedmin | but is it safe to store orm objects in a thread local and have them span multiple transactions? |
| 13:30.04 | mgedmin | "storm caching" is not a very googlable phrase |
| 13:31.41 | mgedmin | (I think I meant "store" when I said "session") |
| 13:35.22 | jkakar | mgedmin: I *think* it should be okay to reuse objects across transactions. |
| 13:36.01 | jkakar | mgedmin: Assuming you only use them in the same thread as the store they belong to, that is. |
| 13:39.42 | mgedmin | hm, if I use a threading.local, I'll have a hard time invalidating caches of other threads |
| 13:53.27 | jkakar | Yeah, sharing data across transactions will introduce cache coherency difficulties. |
| 16:03.47 | *** join/#storm jkakar (~jkakar@252.Red-79-154-167.dynamicIP.rima-tde.net) |
| 18:30.31 | *** join/#storm jkakar (~jkakar@252.Red-79-154-167.dynamicIP.rima-tde.net) |
| 19:08.05 | *** join/#storm jkakar (~jkakar@252.Red-79-154-167.dynamicIP.rima-tde.net) |
| 20:10.10 | *** join/#storm jkakar (~jkakar@252.Red-79-154-167.dynamicIP.rima-tde.net) |
| 20:51.26 | *** join/#storm jkakar (~jkakar@252.Red-79-154-167.dynamicIP.rima-tde.net) |
| 21:42.45 | *** join/#storm jkakar (~jkakar@107.Red-79-151-34.dynamicIP.rima-tde.net) |
| 21:55.21 | *** join/#storm m4v (~znc@unaffiliated/m4v) |
| 22:42.05 | *** join/#storm fcorrea (~fcorrea@201-62-110-55-ma.static.vivax.com.br) |
| 23:02.22 | *** join/#storm m4v (~znc@unaffiliated/m4v) |