Have you confirmed that the database is as expected? Sounds like that's the one thing that's not being covered by your resets. I know AR does (did?) use some db reflection to determine columns. Maybe it's actually a holdover from that behavior (which is vanilla rails btw). In the absence of code/stack trace that's about all I can suggest.
On Nov 11, 9:52 am, Tuishimi <[email protected]> wrote: > I know, I agree, I really do. > > But I've had several other developers look at it and they are baffled > as well. The model does not even contain the fields being referenced > by ActiveRecord. One developer has a thought, but wants to check > something out first... I'll let you know what we find. > > I wish I could show you the code but I cannot... two of the fields > that ActiveRecord references are not even anywhere in my source > tree... > > I do thank you for your responses tho'. > > On Nov 10, 11:49 pm, Domizio Demichelis <[email protected]> wrote: > > > again: > > IF the executed sql is wrong THEN the model is wrong, because the model > > generates the sql > > > ciao > > dd -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
