Re: [web2py] Re: image uploading and storing in web2py

2011-10-17 Thread Bruno Rocha
The recommended is:

Store the pictures on the file system and picture locations in the database.


 Why? Because...

1. You will be able to serve the pictures as static files.
2. No database access or application code will be required to fetch the
pictures.
3. The images could be served from a different server to improve
performance.
4. It will reduce database bottleneck.
5. The database ultimately stores its data on the file system.
6. Images can be easily cached when stored on the file system.


But if it is a requirement to store in database there is not to do about.


On Mon, Oct 17, 2011 at 6:19 AM, Gour g...@atmarama.net wrote:

 On Mon, 17 Oct 2011 05:57:32 -0200
 Bruno Rocha rochacbr...@gmail.com wrote:

  If your image needs to be stored in database (not in filesystem) do:

 Is it, in general, recommended to store image (blob) of such size in the
 {sqlite3,postgresql} database?


 Sincerely,
 Gour


 --
 When your intelligence has passed out of the dense forest
 of delusion, you shall become indifferent to all that has
 been heard and all that is to be heard.

 http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810




-- 



--
Bruno Rocha
[ About me: http://zerp.ly/rochacbruno ]
[ Aprenda a programar: http://CursoDePython.com.br ]
[ O seu aliado nos cuidados com os animais: http://AnimalSystem.com.br ]
[ Consultoria em desenvolvimento web: http://www.blouweb.com ]


Re: [web2py] Re: image uploading and storing in web2py

2011-10-17 Thread Saurabh S
hi thanks for you reply...please tell me how can i store the path of image
into the databse and actuall image image on the file system ?...i mean what
would the field in database.if i go with this approach will i be able to
view the same image when i edit a perticuler client...please reply

On Mon, Oct 17, 2011 at 3:43 PM, Bruno Rocha rochacbr...@gmail.com wrote:

 The recommended is:

 Store the pictures on the file system and picture locations in the
 database.

 Why? Because...

1. You will be able to serve the pictures as static files.
2. No database access or application code will be required to fetch
the pictures.
3. The images could be served from a different server to improve
performance.
4. It will reduce database bottleneck.
5. The database ultimately stores its data on the file system.
6. Images can be easily cached when stored on the file system.


 But if it is a requirement to store in database there is not to do about.


 On Mon, Oct 17, 2011 at 6:19 AM, Gour g...@atmarama.net wrote:

 On Mon, 17 Oct 2011 05:57:32 -0200
 Bruno Rocha rochacbr...@gmail.com wrote:

  If your image needs to be stored in database (not in filesystem) do:

 Is it, in general, recommended to store image (blob) of such size in the
 {sqlite3,postgresql} database?


 Sincerely,
 Gour


 --
 When your intelligence has passed out of the dense forest
 of delusion, you shall become indifferent to all that has
 been heard and all that is to be heard.

 http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810




 --



 --
 Bruno Rocha
 [ About me: http://zerp.ly/rochacbruno ]
 [ Aprenda a programar: http://CursoDePython.com.br ]
 [ O seu aliado nos cuidados com os animais: http://AnimalSystem.com.br ]
 [ Consultoria em desenvolvimento web: http://www.blouweb.com ]




Re: [web2py] Re: image uploading and storing in web2py

2011-10-17 Thread pbreit
Have you reviewed the example in the Book?
http://web2py.com/book/default/chapter/03#An-Image-Blog