#442 ✓resolved
Max Aller

automigrate + sqlite3 broken?

Reported by Max Aller | July 5th, 2008 @ 11:58 PM

When I try doing an automigrate, I get an error "+name+ should be Symbol, but was String". Since at no part in the stacktrace is my code referenced, I'm going to assume for the moment that it couldn't be something in my code. Anyway, here's the stacktrace:


Comments and changes to this ticket

  • Bernerd Schaefer

    Bernerd Schaefer August 1st, 2008 @ 09:47 AM

    • State changed from “new” to “resolved”

    Are you still getting this? I haven't seen any other issues with this, so I'm going to mark this as resolved unless I hear back from you. Thanks.

  • Max Aller

    Max Aller August 8th, 2008 @ 11:37 PM

    Finally got around to getting dm back to a working state (had to manually update rubygems apparently) but I'm still getting this error...

  • Max Aller

    Max Aller August 9th, 2008 @ 12:03 AM

    The cause isn't actually sqlite3, but something a bit more insidious. Still convinced it's a bug though, I'll let you know once I track it down. Stack trace from before still applies.

  • Max Aller

    Max Aller August 9th, 2008 @ 12:09 AM

    So after reviewing the specs, I discovered the problem. I was referring to a :child_key as a 'string' instead of a [:one_element_array_symbol]. Perhaps error-checking for this would be helpful? Your call.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

People watching this ticket

Referenced by