| 00:00.21 | *** join/#storm _mup_ (~mup@li37-90.members.linode.com) |
| 06:08.53 | *** join/#storm jamesh_ (~james@canonical/launchpad/jamesh) |
| 07:10.03 | *** join/#storm stub (~stub@canonical/launchpad/stub) |
| 08:25.28 | *** join/#storm zmijunkie (~sascha@pd95b6fd9.dip0.t-ipconnect.de) |
| 08:27.51 | *** join/#storm fcorrea (~fcorrea@213.215.248.83) |
| 08:50.15 | *** join/#storm bigjools (~quassel@82-71-93-254.dsl.in-addr.zen.co.uk) |
| 08:50.16 | *** join/#storm bigjools (~quassel@canonical/launchpad/bigjools) |
| 09:46.28 | *** join/#storm esteve (~quassel@cli-5b7ee9bd.bcn.adamo.es) |
| 11:10.20 | *** join/#storm niemeyer (~niemeyer@189.73.143.214) |
| 11:10.20 | *** mode/#storm [+o niemeyer] by ChanServ |
| 17:24.07 | *** join/#storm magmatt (~Matt@63-235-131-194.dia.static.qwest.net) |
| 17:47.29 | magmatt | What's the recommended way for executing SQL outside of a transaction? I have been doing storm.commit(); store._connection._raw_connection.execute(...) |
| 18:07.08 | marienz | magmatt: I'd guess "not doing that" (committing immediately instead) |
| 18:09.05 | magmatt | marienz: postgres complains thus "psycopg2.InternalError: CREATE INDEX CONCURRENTLY cannot run inside a transaction block" |
| 18:09.23 | marienz | hrm |
| 18:10.04 | marienz | I don't think there's a way that's actually good. The way you found may be the best one available. |
| 18:12.18 | magmatt | marienz: k, thanks |
| 18:14.04 | marienz | (I'd mention raw_execute, but the sqlite database backend will run BEGIN for you there) |
| 19:23.23 | *** join/#storm niemeyer (~niemeyer@177.27.66.163) |
| 19:23.23 | *** mode/#storm [+o niemeyer] by ChanServ |
| 22:07.24 | *** join/#storm wgrant (~wgrant@ubuntu/member/wgrant) |
| 22:14.34 | *** join/#storm milosn (~milosn@cpc12-rdng20-2-0-cust598.15-3.cable.virginmedia.com) |
| 23:42.24 | *** join/#storm fcorrea (~fcorrea@213.215.248.83) |
| 23:59.56 | *** join/#storm tek0 (~tek@gentoo64.net) |