Reputation: 472
I'm planning to develop web app. to store real estate information.
Tech. details: MSSQL, NHIBERNATE ORM, C#, ASP.NET MVC3
Property will have some properties like
Created, Updated, Id, Name, ... and IList<Photo> Photos.
So here will have one to many relations, one property can have many photos.
On the other side on Photo entity have reference to Property object
and ImageData and ImageMimeType
to store photos in db.
This solution is recommended in apress book mvc3 pro to store images, but I'm wondering what will happen when these database become huge because of images that are stored inside. Any thought are helpful.
Which approach do you use? Db or file path on the server? Any thoughts, links are helpful. thanks
Upvotes: 0
Views: 750
Reputation: 1111
As stated in this article ....
Storing URL is much easier to ADD, EDIT, DELETE, Database size also reduces, as oppose to store image in binary format.
Upvotes: 1