Printable View
Hi all,
I have doc file containing images and i stored it in to database Blob type.
I retrieved that file from database and written the content to new doc file.
but the resultant doc file is not containing images instead it is containing binay data of images. But i want doc file with original images how to solve it
please help me for this.
Storing images in DB is not very good solution.
First it is not natural to store a lot of data in DB that has to be retrieved later.
Second when you store it, you cannot open img file easily from out of DB.
Mostly used approach is to store images on file system, and store their names in DB tables as regular txt or varchar column type.
You have only to match the data in the column with file name in your file system in proper way.
regards :)
Couldn't disagree more.Quote:
Originally Posted by FON
You store data in a database. Images are data.
Now, some DBs are not as good as others at this. I'm not entirely sure it's possible in Access, for example. But Oracle, SQLServer, Postgres work.
As for reading it out of the db? That's just as easy as reading it from a file.
The other advantage of having it in the db is data integrity. The db will now be handling all your data, and not just part of it, so the integrity will be far easier to maintain.
As for lots of data. That's what DBs are for!
Anyway, it appears the OP is storing a .doc file (ie word document), that contains images, and not an image file itself.
So, for the OP, how are you writing this to the db from the doc, and how are you reading it back?
Tolls thank you very much for your post,
i have discussion on this topic with my colleagues
and most things you have written are correct.
This is what forums is about - rethinking and finding good second opinion:)
DB admins told me that this things has to be considered
on file-system vs. DB topic:
1) Cost and capacity - do you use your own DB server or is it hosted somewhere, let's say ISP gives you 50MB in some MySQL DB.
There are folder issues depending on your OS - MAX physical number of files in folder, so you have to make a logic to map filenames from many different dirs to actual files in DB...
2) Speed - indexed paths in File System with help of lucene can increase speed when you compare it to DB file writing. There are many type of file systems for different OSs, some or better to store bigger files...
Rethink how often you do replication and backup of your huge DB if files are in it. Everyone knows hot to copy files to another location and it is fast.
If you backup again, it is even faster - just use SKIP when same file is
to be copied again
3) security - definitely better if files are in DB.
You don't have to think about file and folder permissions,
specially if server is not yours (you use ISP)
Delete, insert, update problems:
If you delete some record in DB that has file associated with it,
you are responsible for writing code that deletes the file from file-system,
or you will have orphan files.
On contrary if file is in DB, you can use it in SQL queries if you need it
and use cascades to delete it easily when parent is deleted.
Think about possibility to move application from Windows to Linux
and problems you may have with different file system nature, permissions...
if you use file system to store your files
Looking forward to here more opinions from forum members
and hope we will solve your problem in further posts ;)
I was begining to think about the task of data movement from one file system to the other and all the details involved(based what FON said)...You made a lot of sense here Tolls.Quote:
Originally Posted by Tolls
Good points, FON.
The places I've worked tend to have their own DBs, and control over hosting, so much of the stuff you mention hasn't affected me. These things are never carved in stone...:)