Forum: Ruby on Rails issue with deprecatiing push_with_attributes

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Brian H. (Guest)
on 2006-04-27 17:13
(Received via mailing list)
I've been listening to the discussions regarding the plans to eliminate
push_with_attributes. While I think it's good practice to make join
models
if you're developing a new system, I can't help but think t hat
push_with_attributes should be left around to deal with legacy
databases.

I might want to wrap my application around a database I don't control.
Making a new join model might not be an option for me (unless there's
something I'm missing).  The linking table may have attributes that I'll
need to change.

I could still get them updated via SQL but that's silly since this is
alredy
handled by AR.

Would anyone care to comment on this? Perhaps the functionality could be
removed from Rails but placed in a *maintained* plugin for legacy
database
support?
Brian H. (Guest)
on 2006-05-03 20:57
(Received via mailing list)
Should this be asked elsewhere?
This topic is locked and can not be replied to.