Forum: Ruby Dealing with old types

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.
05b876a1f205e76fdce882024e0e1630?d=identicon&s=25 richard.mcgrath (Guest)
on 2005-11-18 06:14
(Received via mailing list)
Hi,

I often have tables that refernce a sub-table that contain types.  e.g.
an addresses table might have a field called "address_type_id" that
references a single row in the "address_types" table.

When I display this information a web page with rails, this is all
fine.  However in the address_types table (for example) I would like to
have a boolean column called 'active'.  So that if for new records a
particular type should not be selected, I can add criteria to the SQL
that gets the values to populate a drop down list to only get types
where active = 1 (true).

What I would like some input on is how do I deal with legacy records in
the (for example) addresses table.  When I display old records that
might reference an address type that has been made in-active (e.g it
references a type that has since had its active field set to 0), it
will not find the value in the drop down list.

Does this make sence?

What would be an elegant solution to this problem in rails?

Thanks for any input,
Regards,
Richard
036a1b88dafaab8ffd73a8b0a74b5b38?d=identicon&s=25 ef (Guest)
on 2005-11-18 17:13
(Received via mailing list)
On Fri, Nov 18, 2005 at 02:12:19PM +0900, rmmcgr wrote:
< ... a Rails question ... >

You might get an answer if you ask on the Rails list:
http://lists.rubyonrails.org/mailman/listinfo/rails
This topic is locked and can not be replied to.