On 27 Dec 2008, at 15:10, Matt Jones wrote:
---- The method has been deprecated and removed for a while now, though.
Ah yes, that does make sense.
What attributes are "leaking" in your app? And how do you access them otherwise?
Not my app :-)if you've got foo habtm bars then you get foo_id and bar_id attributes appearing, which you don't care about or ever want to access.
Fred
--Matt Jones On Dec 27, 2008, at 6:49 AM, Frederick Cheung wrote:Is there any reason why HABTM default select clause is select * from ... rather than select table_name.* ... ?As it is attributes from the join table 'leak' into the attributes for the collection you are fetching (which for example makes a mess if youcall to_xml on it). On the other hand has many through does do select table_name.* Is there a specific legacy reason why this is so or is it just historical artificat (ie can we just change it to table_name.*)--~--~---------~--~----~------------~-------~--~----~You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group.To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
smime.p7s
Description: S/MIME cryptographic signature
