I am getting an error when running a migration that is supposed to
create tables called “bottom”, “top”, “left” and “right”. Since “bottom”
and “top” work just fine, my hunch is that in the SQL the “left” is
mistaken for some join statement like “LEFT INNER JOIN”.
Couln’t one consider that a Rails bug? Shouldn’t Rails be able to escape
names that match SQL keywords? Or is it in fact not possible to create
tables named like that?
I am getting an error when running a migration that is supposed to
create tables called “bottom”, “top”, “left” and “right”. Since “bottom”
and “top” work just fine, my hunch is that in the SQL the “left” is
mistaken for some join statement like “LEFT INNER JOIN”.
no I did not have a “left” table yet. Sounds like it’s not an accepted
table name, and I ended up calling it bounds_left instead
Thanks!
Ingo
Darren Beale wrote:
I am getting an error when running a migration that is supposed to
create tables called “bottom”, “top”, “left” and “right”. Since “bottom”
and “top” work just fine, my hunch is that in the SQL the “left” is
mistaken for some join statement like “LEFT INNER JOIN”.