You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering if we really need new table for each file in class? We can use only one table paperclip_database_files which will be in polymorphic association with active record model. cleaner solution imho, what do you think?
The text was updated successfully, but these errors were encountered:
I don't see minimizing number of database tables as a goal by itself... But if it could simplify design and reduce code my ears are open. But I think I need a more detailed/specific proposal.
On my fork I changed the code to store all attachments in one table, in my opinion the idea is much more simple now. Please take a look and share your opinion.
I am wondering if we really need new table for each file in class? We can use only one table
paperclip_database_files
which will be in polymorphic association with active record model. cleaner solution imho, what do you think?The text was updated successfully, but these errors were encountered: