11:08 <limekin> hello

11:09 <jammanbo> lo

11:09 <jammanbo> there's nobody here but you and me ..

11:10 <limekin> is there any good way of keeping migrations and running them in sinatra ?

11:11 <jammanbo> depends on your ORM really. What are you using?

11:11 <limekin> datamapper of course

11:11 <jammanbo> good luck with that

11:12 <jammanbo> there is a dm-migrations gem isnt there? Also, DM is very proactive in creating and modifying your tables, so I've never had the need for migrations

11:13 <jammanbo> oh, sorry limekin, i understand your "of course" now … thought this was the Sinatra chan B)

11:14 <limekin> its okay, so i just create and modify the table structures manually and interact with it using data-mapper ?

11:15 <jammanbo> you dont need to do anything if you've declared your properties in your models. Just run either DataMapper.auto_migrate! or .auto_upgrade! and it'll create/update the tables for you.

11:17 <limekin> thanks for the info

13:56 <jammanbo> shot to nothing … Anyone got thoughts on dm-accepts_nested_attributes and validation errors? Specifically, the issue of the root object being valid even though a deeply nested resource is invalid / the errors being difficult to get to.

13:57 <mkristian> maybe the gem dm-validations-ext helps

13:58 <jammanbo> mkristian: It only goes one level deep :/

13:58 <mkristian> jammanbo, ahh - did not know that limitation

14:23 <jammanbo> Okay … is there a way to ask a resource for the associated resources that it has already loaded?

15:11 <apoc> hi, I have a query like this: Item.all({Item.tags.tagname => ['foo','bar']}) which gives me all items with either the 'foo' or 'bar' tags, how do I query all items that have the 'foo' AND 'bar' tags?

15:12 <mkristian> apoc, I would try: Item.all({Item.tags.tagname => 'foo' }) && Item.all({Item.tags.tagname => 'bar' })

15:16 <apoc> alright, is there no other way?

15:16 <jammanbo> Its a single & isn;it it?

15:17 <apoc> that I can use within the arguments?

15:17 <jammanbo> the above will do what you expect

15:17 <jammanbo> (until you start trying to apply "scopes" to the result)

15:17 <mkristian> jammanbo, probably - I keep on mixing this up

15:21 <apoc> the query is much more complex than that is the problem, with other conditions and dm-pagination

15:22 <jammanbo> so

15:22 <mkristian> apoc, you can add whatever more you need to each argument list

15:23 <jammanbo> you just keep buildind up the query using set operators

15:23 <apoc> ahh okay I think now I got it, thanks everyone

15:27 <jammanbo> like I said, stuff like this aint going to work for you:

15:27 <jammanbo> def self.paged; all.paged(params[:p]).per(20); end

15:27 <jammanbo> (Item.all(…) & Item.all(…)).paged

15:28 <jammanbo> AND YET THE FOLLOWING WILL WORK!

15:28 <jammanbo> (Item.all(…) & Item.all(…)).paged(params[:p]).per(20)

15:28 <jammanbo> bloody datamapper

15:32 <apoc> and no inject to build it dynamically

15:35 <apoc> I thought that would work, tags.map {|tag| Item.all(Item.tags.tagname => tag)}.inject {|a,b| a & b}

15:38 <jammanbo> tags.inject(Item.all) { |q, tag| q & Item.all(tagname: tag) }

15:38 <jammanbo> maybe

15:39 <jammanbo> prettier if nothing else

15:43 <apoc> oh wait there was another bug, that does work!

15:43 <apoc> yep works perfectly now

16:22 <jammanbo> do these words mean anything to anyone: Association, Lazy-Loading, Validation, Heisenbug?

16:28 <onewheelskyward> yes, yes, yes, yes.

16:28 <jammanbo> great!

16:28 <jammanbo> fix it for me

16:28 <jammanbo> :D

16:29 <onewheelskyward> fix what for you? I already answered the question. :)

16:30 <jammanbo> tell me what datamapper expects of me … I ask it if something is valid (it isnt) and says "yeah sure, why not". I look at the invalid thing and then ask it if it's valid, and it says "no"

16:36 <jammanbo> /ragequit

17:05 <onewheelskyward> oh, you mean that thing where the relationships are invalid?

17:05 <onewheelskyward> I ran into that once, but it was my error. It just wasn't exposed.

17:06 <onewheelskyward> ah. They actually did ragequit.