dkubb changed the topic of #datamapper to: Datamapper v1.2.0 | Mailing List: http://is.gd/aa9D | Logs: http://is.gd/qWAL7V | DataMapper 2 Renamed to ROM, see #rom-rb for development
rsim has quit [Quit: Leaving.]
rsim has joined #datamapper
rsim has quit [Ping timeout: 245 seconds]
v1n has joined #datamapper
rsim has joined #datamapper
rsim has quit [Ping timeout: 245 seconds]
rsim has joined #datamapper
rsim has quit [Ping timeout: 245 seconds]
<cvkline>
Holy cow, DataMapper with Ruby warnings on is SCARY!!!
<mbj>
cvkline: Try active record with warnings on ;)
<mbj>
cvkline: Also it highly depends on the version of ruby you run with warnings.
<cvkline>
No thanks. I tried and failed to port a machine with a Rails app on it. It turns out to be INCREDIBLY sensitive to the version numbers of everything it needs.
<cvkline>
The things they changed in the Ruby language between 1.8 and 1.9 is a huge show stopper there.
<mbj>
What version of ruby you plan to run?
<cvkline>
I'm testing on 1.9.3 on Linux... the production platform is brand new Macs with 10.9, which is Ruby 2.0.
<cvkline>
From what I am seeing, 1.9 to 2.0 is not nearly as disruptive as 1.8 to 1.9 was.
rsim has joined #datamapper
rsim has quit [Ping timeout: 245 seconds]
xargoon has quit [Ping timeout: 240 seconds]
<mbj>
yeah
xargoon has joined #datamapper
_808chris has joined #datamapper
<_808chris>
good evening
<_808chris>
any one alive?
<_808chris>
Anyone have any ideas why foo.get(id) would be throwing a "ArgumentError at /
<_808chris>
The number of arguments for the key is invalid, expected 2 but was 1"
<_808chris>
the property is setup like : property :id, Serial
<_808chris>
trace is saying this: ArgumentError - The number of arguments for the key is invalid, expected 2 but was 1: