On Jan 25, 2012, at 1:56 PM, David Chelimsky wrote:
> I'd start by debugging to see where the wheels fall off. Are you
> familiar/comfortable with Ruby's debugger?
Sure.
What’s happening is that during the save process, I get to field_changed? in
dirty.rb, which does
value = column.typ
On Jan 25, 2012, at 1:45 PM, David Chelimsky wrote:
> Just looked back at your initial email and see you cited rspec-2.8,
> but the way Rails handles incoming params in tests changed in either
> 3.1 or 3.2 (I have to check). Which rails version specifically?
3.1.
Since I was *always* going to be
On Jan 25, 2012, at 3:44 AM, Julian Leviston wrote:
> Okay so NOW to me it sounds a lot like you're using a non-integer as a
> primary key which I wouldn't do...
I don’t think you’ve tried to write a server app that synchronizes with
handheld apps over an unreliable internet connection. UUIDs m
On Jan 24, 2012, at 11:27 PM, Julian Leviston wrote:
> On 25/01/2012, at 5:24 PM, Guyren G Howe wrote:
>
>> My code that saves a record works fine in development or production, or from
>> the console. I can take the code in my test and run it in the console, and
>> i
My code that saves a record works fine in development or production, or from
the console. I can take the code in my test and run it in the console, and it
works fine.
But when I run it under a model rspec, the ids are getting set to 0. I’ve
traced it through to where I do:
.create
where I ca
