search for: tableb_id

Hello list, I think I''ve found a bug in the way Rails is talking to my Postgres DB when recording HABTM data. My join_table looks like this: id serial primary key, tablea_id integer references tablea(id), tableb_id integer references tableb(id), other_attributes... When Rails writes to join_table, I''d expect it to do something like: INSERT INTO join_table (tablea_id, tableb_id) values (123,456) or maybe INSERT INTO join_table (id, tablea_id, tableb_id) values (nextval(''join_table_seq'...

...etween tables - auto-generation of a checkbox-driven approach to inputting/updating HABTM relationship data - auto-generation of a checkbox- plus field-driven approach to inputting/updating HABTM relationship data, where the "middle" table has additional fields besides e.g. id, tablea_id, tableb_id By adding these 3 features to base Rails, my feeling is that it would reduce the amount of repetitive coding required by probably 80%. I understand that there''s a reluctance on the part of the core Rails team to extend scaffolds, but I really don''t understand the reason for this...