skade has quit [Quit: Computer has gone to sleep.]
skade has joined #rom-rb
skade has quit [Ping timeout: 272 seconds]
cbuxton_ has quit [Ping timeout: 264 seconds]
cbuxton_ has joined #rom-rb
jgaskins has joined #rom-rb
jgaskins has quit [Quit: This computer has gone to sleep]
jgaskins has joined #rom-rb
jgaskins has quit [Quit: This computer has gone to sleep]
jgaskins has joined #rom-rb
lfox has joined #rom-rb
lfox has quit [Max SendQ exceeded]
jgaskins has quit [Quit: This computer has gone to sleep]
jgaskins has joined #rom-rb
jgaskins has quit [Quit: This computer has gone to sleep]
jgaskins has joined #rom-rb
jgaskins has quit [Quit: This computer has gone to sleep]
jgaskins has joined #rom-rb
jgaskins has quit [Quit: This computer has gone to sleep]
jgaskins has joined #rom-rb
jgaskins has quit [Quit: This computer has gone to sleep]
jgaskins has joined #rom-rb
lfox has joined #rom-rb
lfox has quit [Max SendQ exceeded]
postmodern has joined #rom-rb
lgierth has joined #rom-rb
lfox has joined #rom-rb
jgaskins has quit [Quit: This computer has gone to sleep]
jgaskins has joined #rom-rb
jgaskins has quit [Quit: This computer has gone to sleep]
skade has joined #rom-rb
lfox has quit []
jgaskins has joined #rom-rb
skade has quit [Quit: Computer has gone to sleep.]
skade has joined #rom-rb
skade has quit [Client Quit]
solnic has joined #rom-rb
<xybre>
Apparently it doesn't matter if the SQL is valid, it'll still often create an unwinnable (always empty set) situation, without warning.
<xybre>
I think part of the blame is just mysql, I don't remember ever having all these issues with postgres.
<solnic>
postmodern: re your sql with \n suggestion, we built a new sql generator (github.com/dkubb/sql) which will soon be integrated with axiom. I believe it's gonna be much easier to produce easy-to-read sql using it
<solnic>
postmodern: re your question from Friday - I started rom-rails because I want to build some stupid-simple app using ROM and add/improve things that are missing. It's gonna use memory adapter for now though
<postmodern>
solnic, nice good to hear
jgaskins has quit [Quit: This computer has gone to sleep]
jgaskins has joined #rom-rb
<solnic>
postmodern: seems like we're gonna have a first usable release this year ;)
<postmodern>
solnic, don't jinx it! :)
<solnic>
why, I've been doing that successfuly since 2011 or so ;)
<solnic>
we are gonna release it this year, it's gonna be awesome, people will go crazy omg
<CraigBuchek>
solnic: I'm on this channel to help from that end.
<CraigBuchek>
That's what I'm interested in integrating ROM with Virtus too.
<solnic>
CraigBuchek: thanks
<xybre>
This company I'm working for uses Virtus for its non AR aggregate objects. It's about the only tolerable part of the app tbqh.
<solnic>
we're gonna get there eventually
<solnic>
xybre: oh yeah? that's nice to hear
<solnic>
I've heard many opinions like that
<xybre>
I'm actually not the one who implemented it, I should git blame who it was.
<solnic>
makes me more confident that this whole ROM thing is a good idea ;)
<CraigBuchek>
xybre: I'm also working on integrating Virtus and AR. Hoping that will be a stepping stone to Virtus + ROM.
<solnic>
CraigBuchek: depends how you want to integrate things
<solnic>
the beauty here is that we will be able to have different ways of dealing with stuff
<xybre>
AR is an unholy abomination. I still use DM or something else in my own apps.
<solnic>
people can build all sorts of layers on top of ROM and its underlaying libs
<xybre>
solnic: oh I know. I'm not AR apologist. I've spent most of today writing raw SQL and occassionally refactoring back into AR. I'm hesistant to use Arel directly though.
<xybre>
CraigBuchek: Trying to make a DM1-like system?
<CraigBuchek>
If ROM isn't ready, my next project will probably use either Sequel or Perpetuity.
<solnic>
CraigBuchek: hah, this is interesting, feels like DM1 :)
<CraigBuchek>
Yeah, basically.
<solnic>
that's cool, I wanted to do it too FOR FUN
<solnic>
personally I would use it probably, I'm so over AR
<CraigBuchek>
Trying to DRY up the common case where the mapping and the class are basically the same.
<solnic>
CraigBuchek: re ROM being ready - I kinda changed my approach this year as I burned out completely last year
<solnic>
so this year I'm gonna focus on making it usable for some use cases
<solnic>
that's why I started rom-rails
<xybre>
solnic: bottom up :)
<solnic>
I just need some basic scenario where ROM can be used
<CraigBuchek>
solnic: I know. I follow you in twitter. Sad to see you have to do that, but glad you're doing what's right for you.
<solnic>
our goals are, excuse the language, fucking huge, so it's gonna take us YEARS to get there
<solnic>
yes, more years, that's what I said
<solnic>
focusing on those was too hard for me so I'm gonna take it easy this time
<CraigBuchek>
I think it would help, as you're discovering, to look at things from the top down.
<CraigBuchek>
You guys seem very bottom up oriented, and do a great job there.
<xybre>
I mean, I'd like to use it for every major use case I have where I'd use DM1 or AR or Mongoid or etc.
<CraigBuchek>
But it seems like sometimes you guys are too focused down there.
<xybre>
A Redis ORM would be awesome to work into an intelligent caching system.
<solnic>
CraigBuchek: I agree that's why I decided to change approach as we reached a point where we really need to experiment on the higher layers
<solnic>
xybre: there's axiom-redis-adapter somewhere on github
<CraigBuchek>
solnic: Do you have a real-life Rails project that you're working on to facilitate that?
<solnic>
CraigBuchek: I have one project I always wanted to port from rails/dm1 to rom but it's not oss
<solnic>
I will probably write something simple for demo purposes and experimentation :)
<solnic>
something OSS
<CraigBuchek>
Sounds good.
<CraigBuchek>
I might help on that, or fork it and see how Virtus::ROM works with it.
<xybre>
40 lines with database access and does a simple task, thats great, I wish I could do more things like that.
<solnic>
xybre: you'll be able to rewrite this using rom once the new sql generator is integrated with axiom and we finally add WRITE support :D
<postmodern>
re ROM + Virtus integration
<postmodern>
i definitely want to replace my parameters lib with virtus
<postmodern>
but i hope ROM will differentiate between which virtus are mapped/persisted and which are instance only
<solnic>
postmodern: well that's up to you to define
<xybre>
solnic: being able to write out be.. helpful. Haha. Still, I can think of a lot of uses for read-only adapaters.
<solnic>
you tell the mapper what is mapped and what is not
<jgaskins>
solnic/CraigBuchek: I've been thinking of putting up a Rails project on GitHub to demonstrate patterns I've found that work well with Perpetuity. Maybe it might be a good idea to do the same with ROM?
<xybre>
I think I'll have the most fun with generating quries with axiom.
<jgaskins>
solnic: have you guys found some good patterns of use yet?
<xybre>
ie NOT writing SQL.
<solnic>
jgaskins: nope not yet
<solnic>
I know that snusnu is building an app using ROM already
<solnic>
with a mixture of DM1
<solnic>
and mbj built some systems using his data mappers too
<solnic>
we should definitely collaboratae
<solnic>
here
<jgaskins>
solnic: awesome
<jgaskins>
solnic: also, speaking of collaborating … we're terrible at getting together for pairing.
<solnic>
jgaskins: tell me about it
<CraigBuchek>
I'm "practicing" with Virtus integrating with perpetuity.
<jgaskins>
CraigBuchek: Virtus and Perpetuity work very well together.
<CraigBuchek>
jgaskins: Have you been using my virtus-perpetuity gem, or something else?
<xybre>
jgaskins: do you have any code online using it?
<jgaskins>
CraigBuchek: nah, just using the two gems on their own.
<jgaskins>
xybre: using perpetuity?
<xybre>
jgaskins: yep
<jgaskins>
xybre: not yet. but that's what i want to put out. I want to show people how I use it personally because i'm really bad at documentation.
<solnic>
ok it's getting late here. gotta run. good night!
<jgaskins>
later solnic
<xybre>
jgaskins: Well you're in good company with these guys ;)
<jgaskins>
lol actually all the ROM crew are pretty good at documentation. they put YARD docs in all their stuff.
<solnic>
jgaskins: btw we will pair one day and when that day comes we will rewrite all freaking gems on rubygems.org and rule the earth. I think. ok cheers
<jgaskins>
solnic: lol
<jgaskins>
actual lol
<xybre>
jgaskins: There's API documentation, but very little setup and usage documentation.
solnic has quit [Quit: Leaving...]
<jgaskins>
xybre: ah, i think that's mainly because they've been mostly focusing on the lower-level details. that's what solnic was saying, he wants to start working on the higher-level parts to find some good patterns to use in real apps.
<xybre>
jgaskins: I think so too. And the DM1 documentation (and website) was pretty good. And I'll be contributing documentation as soon as things settle down and I've been able to use more of the projects myself.
<jgaskins>
it's also one of the reasons solnic and i want to pair. they've got the good ideas for the lower-level stuff and i've already got a lot of the top-level usage figured out. we want to allow both projects to learn from each other.
<jgaskins>
xybre: awesome. if you get stuck on anything with perpetuity (on any of the adapters), let me know.
lgierth has quit [Quit: Ex-Chat]
<xybre>
jgaskins: I am quite excited about you guys working together for exactly that reason. :)