Comments on: Unexpected “parse error, unexpected tINTEGER Object” Error

By: Do not name table columns “type” in Rails « SNBlog

Do not name table columns “type” in Rails « SNBlog — Fri, 14 Mar 2008 21:01:58 +0000

[...] March 14, 2008 Or error emissions ensue: Chris tells you why. [...]

By: Igor

Igor — Mon, 03 Mar 2008 23:07:25 +0000

Thanks you very much!
You saved a lot of my time!

By: tayfun

tayfun — Wed, 21 Nov 2007 01:41:32 +0000

Thanks a bunch. I couldn’t see this was the problem.

By: Jason Cabot

Jason Cabot — Wed, 04 Jul 2007 10:59:02 +0000

Hi,

Thank You, Thank You, Thank You…

It’s just a pity that rails doesn’t make things like this more obvious – From that error I would never have thought that the problem was with a column name!!

By: Marcus Floriano

Marcus Floriano — Wed, 14 Mar 2007 04:08:07 +0000

Hi,

I had the same problem, it could never imagine that this was problem.

Thank you very much.

By: chris

chris — Sun, 11 Mar 2007 22:40:28 +0000

Glad I could be of help

By: Edd

Edd — Sun, 11 Mar 2007 21:47:17 +0000

I love you. I’ve been spending hours trying to figure this out, and a random search across the interweb found this. We shall spread the word! The sanity of developers across the globe depend on us.