IRC log for #storm on 20090929

01:19.45*** join/#storm EsCoVa (n=gabriel@201.82.142.27)
01:20.02*** part/#storm EsCoVa (n=gabriel@201.82.142.27)
02:01.24*** join/#storm hazmat (n=kapil@plone/hazmat)
02:50.41*** join/#storm vvinet (n=vince@modemcable041.205-203-24.mc.videotron.ca)
03:11.34*** join/#storm hazmat (n=kapil@plone/hazmat)
03:18.03*** join/#storm stub (n=stub@ppp-58-8-3-163.revip2.asianet.co.th)
04:22.27*** join/#storm fcorrea_ (n=fcorrea@189-54-33-8-nd.cpe.vivax.com.br)
05:24.39*** join/#storm jukart (i=lovely@81.189.156.94)
05:29.19*** join/#storm stub (n=stub@ppp-58-8-3-163.revip2.asianet.co.th)
08:53.24*** join/#storm stub (n=stub@ppp-58-8-3-163.revip2.asianet.co.th)
10:12.50*** join/#storm zmijunkie (n=chatzill@i59F5DD76.versanet.de)
11:40.30*** join/#storm srichter_ (n=quassel@c-76-19-135-180.hsd1.ma.comcast.net)
11:47.39*** join/#storm rockstar (n=rockstar@starscream.eventuallyanyway.com) [NETSPLIT VICTIM]
11:58.11*** join/#storm bigdog (n=scmikes@72-197-8-8-arpa.cust.cinci.current.net)
12:16.36*** join/#storm oubiwann (n=oubiwann@c-24-8-208-199.hsd1.co.comcast.net)
12:27.19*** join/#storm andrea-bs (n=andrea@ubuntu/member/beeseek.developer.andrea-bs)
12:35.46*** join/#storm niemeyer (n=niemeyer@200-103-139-122.ctame705.dsl.brasiltelecom.net.br)
12:39.39*** join/#storm mup_ (n=mup@li37-90.members.linode.com)
12:59.06*** join/#storm hazmat (n=kapil@plone/hazmat)
13:11.19*** join/#storm Zenom (n=Zenom@unaffiliated/aj1973)
13:16.09*** join/#storm sidnei (n=sidnei@plone/dreamcatcher)
13:40.27*** join/#storm sidnei (n=sidnei@plone/dreamcatcher)
13:52.59*** join/#storm sidnei_ (n=sidnei@200-203-8-10.cslce701.dsl.brasiltelecom.net.br)
13:56.47*** join/#storm srichter (n=quassel@mail.hcp.com)
14:45.50*** join/#storm fcorrea (n=fcorrea@187.3.157.0)
15:12.06*** join/#storm srichter (n=quassel@c-76-19-135-180.hsd1.ma.comcast.net)
15:48.47*** join/#storm srichter (n=quassel@c-76-19-135-180.hsd1.ma.comcast.net)
16:22.39*** join/#storm fcorrea_ (n=fcorrea@187.3.157.0)
16:58.06*** join/#storm jukart (n=jukart@d86-32-163-51.cust.tele2.at)
17:01.29*** join/#storm andrea-bs (n=andrea@ubuntu/member/beeseek.developer.andrea-bs)
18:16.56*** join/#storm jukart (n=jukart@86.32.163.51)
18:24.45Zenomis there by chance anyway to dump a current schema for storm?
18:24.56ZenomSo I don't have to hand code it all? :)
18:25.16jkakarZenom: No, there isn't.
18:47.26*** join/#storm jukart_ (i=lovely@81.189.156.94)
19:24.24*** join/#storm NottsMancs (n=limeydri@94-195-128-166.zone9.bethere.co.uk)
19:27.52*** join/#storm keppla1 (n=keppla@87.123.49.52)
20:09.06NottsMancshi, anyone arond to answer a couple of queries
20:14.18jkakarNottsMancs: What's up?
20:33.28ZenomHow do I get all rows, because doing like store.find(MyModel)
20:33.34Zenomisn't doing it.
20:46.52jkakarZenom: That's how you do it.
20:47.09jkakarZenom: result = store.find(MyModel); all_mymodel_objects = list(result)
20:47.45jkakarZenom: The ResultSet is lazily evaluated, so results aren't actually fetched from the database until your iterate the ResultSet (or use one of the other methods like one(), any(), etc.).
20:48.06NottsMancsi was wondering if anyone had used sqlalchemy or sqlobject and can give their impressions of those compared to Storm
20:48.22jkakarZenom: If you're wonder what's going on under the hood you can from storm.tracer import debug; debug(True) to see the SQL being run by Storm.
20:48.47NottsMancssqlalchemy uses data mapper pattern, does storm use activerecord# /
20:49.00jkakarNottsMancs: I haven't looked at SQLAlchemy in about 3 years, and my understanding is that it's changed a lot.  I've never used SQLObject.  So, sorry, not much I can offer you. :(
20:50.16NottsMancsbut u happy with Storm
20:50.32NottsMancs?
20:50.36jkakarNottsMancs: Very. :)
20:50.49jkakarNottsMancs: But then, I've been helping out with the project since it's inception, so I'm very biased. :)
20:51.01jkakarNottsMancs: Have you read the tutorial?
20:51.12jkakarNottsMancs: That'll give you a sense of how it works.
20:51.28NottsMancsjkakar: :), ok, why in particular did you choose to use and even contribute to it, do you work fo r Canonical ?
20:51.34NottsMancslol
20:51.35NottsMancs:)
20:54.43jkakarNottsMancs: I work for Canonical, yes. :)
20:54.52jkakarNottsMancs: On the team where Storm originated.
20:55.05jkakarNottsMancs: That said, knowing what I know of Storm, I would use it even if I didn't work for Canonical.
20:57.37NottsMancsjkakar: cool, so you work with Gustavo
20:57.56jkakarNottsMancs: I do, yes.
20:58.28NottsMancsjkakar: wish I worked somewhere cool
20:58.34NottsMancs:P
20:59.17NottsMancsjkakar: Is it a good place to work, Canonical
21:04.53jkakarNottsMancs: It's very cool place to work, yeah.  I feel very fortunate to be part of it.
21:07.36*** join/#storm shaunm_ (n=shaunm@c-98-212-133-244.hsd1.il.comcast.net)
21:13.36*** join/#storm gabriel (n=gabriel@mc-189-95.IPReg.mcmaster.ca)
21:37.31*** join/#storm oubiwann (n=oubiwann@c-24-8-208-199.hsd1.co.comcast.net)
22:03.28*** join/#storm gabriel (n=gabriel@mc-126-100.IPReg.McMaster.CA)
22:08.44*** join/#storm hazmat (n=kapil@plone/hazmat)
23:00.00*** join/#storm darkstar_ (n=nobody@198.Red-213-98-22.staticIP.rima-tde.net)
23:00.11darkstar_hello everybody
23:00.26darkstar_could anybody help me with set?
23:00.49darkstar_I'm trying to update an object, but I don't know why, storm is creating a new one
23:11.10darkstar_I do this
23:11.17darkstar_<PROTECTED>
23:11.17darkstar_<PROTECTED>
23:11.17darkstar_<PROTECTED>
23:19.56jkakardarkstar_: Is that final line supposed to be articulo.set?
23:20.23darkstar_yes it's well write
23:20.35darkstar_I want mean it's good on my code
23:21.26jkakardarkstar_: In that case, your call to .set looks okay... are you sure there's no other reason a new object is being created?
23:21.35jkakardarkstar_: Also, all those calls to unicode() are pretty suspicious. :)
23:21.50darkstar_suspicious of what
23:22.30darkstar_it's wright
23:22.32jkakardarkstar_: Well, you're blindly casting some (I assume non-unicode) data to unicode... if it's always ASCII I guess you're fine, but what if it's UTF-8?
23:22.39jkakardarkstar_: Okay. :)
23:22.44darkstar_no, everything is ok
23:22.46darkstar_problem is set
23:22.48darkstar_or store
23:23.20darkstar_I've create a store beffore for add other objects
23:23.20jkakardarkstar_: Well, it looks like you're using the API correctly.
23:23.20darkstar_and later on I update this one
23:23.35darkstar_before update the last one I do a flush and a commit
23:23.37jkakardarkstar_: If you could write a minimal reproducible example that demonstrates the behaviour you're seeing, that would be very helpful.
23:23.43darkstar_after that I only close the store
23:24.11darkstar_I can do it, but you mabe preffer I paste it in other place...
23:24.25darkstar_if you tell me where can I paste it, I'll do it right now
23:25.26jkakardarkstar_: pastebin.ubuntu.com is cool, please.
23:25.37darkstar_ok
23:31.07darkstar_http://pastebin.ubuntu.com/281734/
23:31.20darkstar_of course at the begining I've created the store
23:31.22jkakardarkstar_: I'm looking...
23:31.27darkstar_thanks you very much, jkakar
23:31.51darkstar_I'm trying to solve it since 3pm
23:32.03darkstar_now here it's 1:30am
23:32.11jkakardarkstar_: Is this Spanish? :)
23:32.22darkstar_more or less
23:32.23darkstar_hehe
23:32.25jkakarhehe
23:32.26jkakarNice.
23:32.33jkakarI was in Barcelona in the spring... it was awesome.
23:32.46darkstar_it's so far of here
23:33.02darkstar_between 300-400km
23:33.09darkstar_barcelona is wonderfull
23:33.14darkstar_but I'm from seville
23:33.21darkstar_much better :P
23:35.09jkakardarkstar_: Ah nice, my wife and I spent an afternoon/night in Seville.  It was beautiful. :)
23:35.29jkakardarkstar_: Okay, so I'm noticing first of all that there's no call to store.commit before you call store.close.
23:35.39jkakardarkstar_: But that doesn't explain the behaviour you've described so far.
23:35.45darkstar_mmm
23:35.48darkstar_yes I do
23:35.50darkstar_wait
23:35.57darkstar_<PROTECTED>
23:35.57darkstar_<PROTECTED>
23:35.57darkstar_<PROTECTED>
23:35.57darkstar_<PROTECTED>
23:35.57darkstar_<PROTECTED>
23:36.00darkstar_<PROTECTED>
23:36.02darkstar_sorry
23:36.16darkstar_commit is because of I add few object to db
23:36.20jkakardarkstar_: What happens if you put a store.commit() before the store.close()?
23:36.36darkstar_it is before commit
23:36.46darkstar_and before set
23:37.09jkakardarkstar_: By not calling it after the .set() call you are effectively discarding the changes from the UPDATE issues as a result of calling .set().
23:37.24darkstar_oh, do you mean call it again?
23:37.25darkstar_ok
23:37.31darkstar_2 times then?
23:37.35jkakardarkstar_: Basically, any changes you make will only be written (permanently) to the database when you call commit.  Storm does everything in transactions.
23:38.13jkakardarkstar_: I don't think you need either the call to flush or commit that you already have, unless there's a reason you want the character_article object to be added in a different transaction.
23:38.39darkstar_same result
23:39.00darkstar_mmmmm
23:39.02darkstar_mabe not there
23:39.04jkakarHehe
23:39.07darkstar_but later on I add tags
23:39.13darkstar_and tags are created there
23:39.24darkstar_tags have a relation n:m with articles
23:39.42darkstar_so I've to flush it because I need to now their ids
23:39.43jkakarOkay.
23:39.45darkstar_isn't it?
23:39.53jkakarGenerally speaking, you shouldn't have to manual flushing.
23:39.55darkstar_so problem souldn't be it
23:40.04jkakarStorm will do it for you when you request the .id attribute of a new object.
23:40.19darkstar_oh, perfect
23:40.29darkstar_but do you think this is the problem?
23:40.32jkakarThere are some cases where you may need to do it manually, but they are rare.
23:40.41jkakardarkstar_: No, I don't think it's a problem here.
23:48.48jkakardarkstar_: http://pastebin.ubuntu.com/281740/
23:49.12jkakardarkstar_: I've written a simple example to demonstrate that .set works correctly.  Maybe it'll help you figure out what's going on with your code?
23:51.04darkstar_you aren't commiting at the end
23:51.05darkstar_does it workds?
23:51.09darkstar_works
23:51.28jkakardarkstar_: Well, it's using an in-memory SQLite database, so committing is abit pointless... :)
23:51.42jkakardarkstar_: But yeah, if it was real code I would add a store.commit() at the end.
23:52.09jkakardarkstar_: But it also demonstrates that flushing behaviour works without manual intervention.
23:56.25darkstar_it still doesn't work!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
23:58.19jkakar:(
23:58.33jkakardarkstar_: The next best way I can help you is if you provide an exampl ehtat I can actually run.
23:59.32darkstar_I've seeying that problem is here
23:59.43darkstar_<PROTECTED>
23:59.45darkstar_...
23:59.46darkstar_else:

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.