| 00:00.44 | *** join/#storm wallflower (n=wallflow@ip-205-246-113-216.pool.grokthis.net) |
| 05:14.25 | *** join/#storm ubot3 (n=ubot3@unaffiliated/nalioth/bot/ubot3) |
| 05:20.21 | *** join/#storm oubiwann (n=oubiwann@97-119-4-118.omah.qwest.net) |
| 05:54.18 | *** join/#storm jukart (n=jukart@lsfw01.lovelysystems.com) |
| 05:57.37 | *** join/#storm andrea-bs (n=andrea@ubuntu/member/beeseek.developer.andrea-bs) |
| 06:31.55 | *** join/#storm dobee (n=dobee@lsfw01.lovelysystems.com) |
| 07:42.59 | *** join/#storm jukart (n=jukart@lsfw01.lovelysystems.com) |
| 07:43.02 | *** join/#storm dobee (n=dobee@lsfw01.lovelysystems.com) |
| 08:39.43 | *** join/#storm mcella (n=mcella@ip-176-30.sn2.eutelia.it) |
| 08:54.22 | *** join/#storm andrea-bs (n=andrea@ubuntu/member/beeseek.developer.andrea-bs) |
| 09:15.09 | *** join/#storm mcella_ (n=mcella@ip-177-193.sn2.eutelia.it) |
| 10:42.40 | *** join/#storm andrea-bs (n=andrea@ubuntu/member/beeseek.developer.andrea-bs) |
| 11:22.11 | *** join/#storm dobee (n=dobee@lsfw01.lovelysystems.com) |
| 12:04.40 | *** join/#storm lightyear (n=ben@nat/fluendo/x-f9e0803a422bf2b5) |
| 12:04.51 | lightyear | therve: big, big, big issue |
| 12:04.54 | lightyear | performance wise |
| 12:05.13 | lightyear | the thing we did to not have the problems with the lazy queries |
| 12:05.22 | lightyear | leads to a very bad performance on doing a commit |
| 12:05.46 | lightyear | from ~0.1s it takes usually up to 10seconds |
| 13:17.40 | *** join/#storm kov (n=kov@debian/developer/kov) |
| 13:38.35 | *** join/#storm hklv (n=hklv@199.84.162.114) |
| 13:50.36 | therve | lightyear: do you have an example to show me? |
| 13:53.20 | therve | I can't think of anything taking 10 seconds, except if you have *a lot* of data |
| 14:26.57 | *** join/#storm andrea-bs (n=andrea@ubuntu/member/beeseek.developer.andrea-bs) |
| 14:36.04 | *** join/#storm bigdo2 (n=scmikes@72-197-8-8-arpa.cust.cinci.current.net) |
| 14:50.28 | *** join/#storm jukart (n=jukart@lsfw01.lovelysystems.com) |
| 14:57.22 | hklv | Hello Storm experts. Storm is said to "works well with existing database schemas". Is there an example somewhere? |
| 14:57.57 | radix | hklv: pretty much every example is an example of working with an existing database schema |
| 14:58.16 | radix | hklv: because Storm doesn't do schema management; you have to create your schema yourself, and then define the Python classes such that they match it. |
| 14:58.28 | lightyear | therve: well, the issue is for me that I have a task coiterater creating objects so they stay in memory and very fast I receive the 100 in alive object |
| 14:59.18 | lightyear | if you want I write a nice test for it... the problem is that it is not easy to make it fail... maybe with a timeout.. |
| 15:00.08 | therve | lightyear: even an example that takes a long time would be nice |
| 15:03.00 | lightyear | therve... second... |
| 15:11.25 | hklv | radix: Is there a ORM that can automatically create its Python classes according to an existing schema? |
| 15:28.44 | lightyear | therve: aaaaaaaaarg.... can't reproduce it with the script |
| 18:26.31 | *** join/#storm jukart (n=jukart@85-124-221-45.static.xdsl-line.inode.at) |
| 20:40.06 | *** join/#storm reacocard (n=reacocar@rccy-06-1010.dsl.iowatelecom.net) |