Why is HABTM generating queries that include an 'id' column?

Figured it out. I'm using Microsoft SQL on the back end. This has been one of the many nuances of working with Microsoft SQL The problem was that I had a table "dbo.

Permissions_roles" that included an id field from prior experimentation. The table that actually had the data in it was "rails_sa. Permissions_roles" that did not include the id (rails_sa is the name of my schema and user that connects) For some reason that I still can't explain, the data behind the models was getting stored in rails_sa.

Permissions_roles. But, the join table definition was coming from dbo. Permissions_roles.

I'm sure there is a rational explanation to this edge case.

Figured it out. I'm using Microsoft SQL on the back end. This has been one of the many nuances of working with Microsoft SQL.

The problem was that I had a table "dbo. Permissions_roles" that included an id field from prior experimentation. The table that actually had the data in it was "rails_sa.

Permissions_roles" that did not include the id (rails_sa is the name of my schema and user that connects). For some reason that I still can't explain, the data behind the models was getting stored in rails_sa. Permissions_roles.

But, the join table definition was coming from dbo. Permissions_roles. I'm sure there is a rational explanation to this edge case.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.