Thanks for the reply. I will mainly store files with 100kb to 250kb not bigger than this. PQescapeByteaConn is not available in a default installation of PostgreSQL? My hosting account hava a standard installation of PostgreSQL. There are other options for escaping binary files? Best Regards, On Tue, Jan 25, 2011 at 10:58 PM, Dmitriy Igrishin <dmitigr@xxxxxxxxx> wrote: > > > 2011/1/26 Andre Lopes <lopes80andre@xxxxxxxxx> >> >> Thanks for all the reply's. >> >> I will be using PHP for now to insert data. >> >> So I shouldn't use base64 to store images or any other kind of files. >> I'm new to storing files in the database. This will be my first >> experience. > > You may want to use large objects to store files instead of using > bytea data type. With large objects you can achieve streaming > data transfer and as of PostgreSQL 9.0 it is possible to control > access permissions on large objects via GRANT. > > But I don't know about support of large objects in PHP. >> >> I will research about PQescapeByteaConn. >> >> Thanks for the help. >> >> Best Regards, >> >> >> On Tue, Jan 25, 2011 at 10:46 PM, Bill Moran <wmoran@xxxxxxxxxxxxxxxxx> >> wrote: >> > In response to Peter Geoghegan <peter.geoghegan86@xxxxxxxxx>: >> > >> >> On 25 January 2011 22:27, Andre Lopes <lopes80andre@xxxxxxxxx> wrote: >> >> > Hi, >> >> > >> >> > I need to put some images on Base64 in a PostgreSQL database. Wich >> >> > type should I use and what is the difference between using bytea or >> >> > text to store Base64? >> >> >> >> I really don't think you want to do that. Base64 is used to make >> >> binary data 7-bit safe for compatibility with legacy systems (i.e. to >> >> embed arbitrary binary data within ASCII). Sometimes people escape >> >> binary data as base64 to store it in their DB, but they typically >> >> store it as bytea. Base64 probably isn't even a particularly good >> >> choice for escaping binary, let alone storing it. >> >> >> >> You should just use a generic escaping function. libpq has >> >> PQescapeByteaConn(), for example. >> > >> > A warning: last I checked, PHP's pg_escape_bytea() was broken, so be >> > cautious if you're using PHP. >> > >> > -- >> > Bill Moran >> > http://www.potentialtech.com >> > http://people.collaborativefusion.com/~wmoran/ >> > >> >> -- >> Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-general > > > > -- > // Dmitriy. > > > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general