Thread

1. Re: Record

   wsheldah@lexmark.com — 2001-10-24T15:42:31Z

   
   If you're using Perl and the DBD::Pg driver, then you can use bytea without
   worrying about escaping anything, since the driver takes care of it.
   
   
   
   
   Alvaro Herrera <alvherre%atentus.com@interlock.lexmark.com> on 10/24/2001
   10:22:39 AM
   
   To:   Aasmund Midttun Godal <postgresql%envisity.com@interlock.lexmark.com>
   cc:   julio%bntsoft.com.br@interlock.lexmark.com,
         pgsql-general%postgresql.org@interlock.lexmark.com (bcc: Wesley
         Sheldahl/Lex/Lexmark)
   Subject:  Re: [GENERAL] Record
   
   
   On Tue, 23 Oct 2001, Aasmund Midttun Godal wrote:
   
   > I am not sure I understand what you mean. However if you are wanting to store
   an image in a table you have 2 options:
   >
   > 1. bytea fields.
   > 2. large objects.
   
   Third option is to encode the image (base64?) and then store as text.
   It's probably slower (since you have to decode it everytime), uses much
   more space, but you don't have to worry about escaping the byte
   sequence.
   
   --
   Alvaro Herrera (<alvherre[@]atentus.com>)
   Jajaja! Solo hablaba en serio!
   
   
   
   
   
   

2. Re: Record

   Aasmund Midttun Godal <postgresql@envisity.com> — 2001-10-24T22:41:11Z

   It handles the unescaping, but you have to escape to update/insert, I use:
   
   s/([^\w])/sprintf("\\%03o", ord($1))/eg;
    
   On Wed, 24 Oct 2001 11:42:31 -0400, wsheldah@lexmark.com wrote:
   > 
   > 
   > If you're using Perl and the DBD::Pg driver, then you can use bytea without
   > worrying about escaping anything, since the driver takes care of it.
   > 
   > 
   > 
   > 
   > Alvaro Herrera <alvherre%atentus.com@interlock.lexmark.com> on 10/24/2001
   > 10:22:39 AM
   > 
   > To:   Aasmund Midttun Godal <postgresql%envisity.com@interlock.lexmark.com>
   > cc:   julio%bntsoft.com.br@interlock.lexmark.com,
   >       pgsql-general%postgresql.org@interlock.lexmark.com (bcc: Wesley
   >       Sheldahl/Lex/Lexmark)
   > Subject:  Re: [GENERAL] Record
   > 
   > 
   > On Tue, 23 Oct 2001, Aasmund Midttun Godal wrote:
   > 
   > an image in a table you have 2 options:
   > 
   > Third option is to encode the image (base64?) and then store as text.
   > It's probably slower (since you have to decode it everytime), uses much
   > more space, but you don't have to worry about escaping the byte
   > sequence.
   > 
   > --
   > Alvaro Herrera (<alvherre[@]atentus.com>)
   > Jajaja! Solo hablaba en serio!
   > 
   > 
   > 
   > 
   > 
   > ---------------------------(end of broadcast)---------------------------
   > TIP 4: Don't 'kill -9' the postmaster
   
   Aasmund Midttun Godal
   
   aasmund@godal.com - http://www.godal.com/
   +47 40 45 20 46
   
   

3. Re: Record

   Aasmund Midttun Godal <postgresql@envisity.com> — 2001-10-24T22:41:11Z

   It handles the unescaping, but you have to escape to update/insert, I use:
   
   s/([^\w])/sprintf("\\%03o", ord($1))/eg;
    
   On Wed, 24 Oct 2001 11:42:31 -0400, wsheldah@lexmark.com wrote:
   > 
   > 
   > If you're using Perl and the DBD::Pg driver, then you can use bytea without
   > worrying about escaping anything, since the driver takes care of it.
   > 
   > 
   > 
   > 
   > Alvaro Herrera <alvherre%atentus.com@interlock.lexmark.com> on 10/24/2001
   > 10:22:39 AM
   > 
   > To:   Aasmund Midttun Godal <postgresql%envisity.com@interlock.lexmark.com>
   > cc:   julio%bntsoft.com.br@interlock.lexmark.com,
   >       pgsql-general%postgresql.org@interlock.lexmark.com (bcc: Wesley
   >       Sheldahl/Lex/Lexmark)
   > Subject:  Re: [GENERAL] Record
   > 
   > 
   > On Tue, 23 Oct 2001, Aasmund Midttun Godal wrote:
   > 
   > an image in a table you have 2 options:
   > 
   > Third option is to encode the image (base64?) and then store as text.
   > It's probably slower (since you have to decode it everytime), uses much
   > more space, but you don't have to worry about escaping the byte
   > sequence.
   > 
   > --
   > Alvaro Herrera (<alvherre[@]atentus.com>)
   > Jajaja! Solo hablaba en serio!
   > 
   > 
   > 
   > 
   > 
   > ---------------------------(end of broadcast)---------------------------
   > TIP 4: Don't 'kill -9' the postmaster
   
   Aasmund Midttun Godal
   
   aasmund@godal.com - http://www.godal.com/
   +47 40 45 20 46
   
   

4. Re: Record

   Alex Pilosov <alex@pilosoft.com> — 2001-10-25T01:42:28Z

   No, you don't, just bind variable as SQL_BINARY, and it'll do the escaping
   on its own. Search archives. :)
   
   -alex
   On Wed, 24 Oct 2001, Aasmund Midttun Godal wrote:
   
   > It handles the unescaping, but you have to escape to update/insert, I use:
   > 
   > s/([^\w])/sprintf("\\%03o", ord($1))/eg;
   >  
   > On Wed, 24 Oct 2001 11:42:31 -0400, wsheldah@lexmark.com wrote:
   > > 
   > > 
   > > If you're using Perl and the DBD::Pg driver, then you can use bytea without
   > > worrying about escaping anything, since the driver takes care of it.
   > > 
   > > 
   > > 
   > > 
   > > Alvaro Herrera <alvherre%atentus.com@interlock.lexmark.com> on 10/24/2001
   > > 10:22:39 AM
   > > 
   > > To:   Aasmund Midttun Godal <postgresql%envisity.com@interlock.lexmark.com>
   > > cc:   julio%bntsoft.com.br@interlock.lexmark.com,
   > >       pgsql-general%postgresql.org@interlock.lexmark.com (bcc: Wesley
   > >       Sheldahl/Lex/Lexmark)
   > > Subject:  Re: [GENERAL] Record
   > > 
   > > 
   > > On Tue, 23 Oct 2001, Aasmund Midttun Godal wrote:
   > > 
   > > an image in a table you have 2 options:
   > > 
   > > Third option is to encode the image (base64?) and then store as text.
   > > It's probably slower (since you have to decode it everytime), uses much
   > > more space, but you don't have to worry about escaping the byte
   > > sequence.
   > > 
   > > --
   > > Alvaro Herrera (<alvherre[@]atentus.com>)
   > > Jajaja! Solo hablaba en serio!
   > > 
   > > 
   > > 
   > > 
   > > 
   > > ---------------------------(end of broadcast)---------------------------
   > > TIP 4: Don't 'kill -9' the postmaster
   > 
   > Aasmund Midttun Godal
   > 
   > aasmund@godal.com - http://www.godal.com/
   > +47 40 45 20 46
   > 
   > ---------------------------(end of broadcast)---------------------------
   > TIP 4: Don't 'kill -9' the postmaster
   > 
   >