Re: Toast, Text, blob bytea Huh?
От | ryan_rs@c4.com (Ryan) |
---|---|
Тема | Re: Toast, Text, blob bytea Huh? |
Дата | |
Msg-id | 7299ab58.0109040832.24776bfb@posting.google.com обсуждение исходный текст |
Ответ на | Re: Toast, Text, blob bytea Huh? ("Joe Conway" <joseph.conway@home.com>) |
Ответы |
Re: Toast, Text, blob bytea Huh?
|
Список | pgsql-hackers |
joseph.conway@home.com ("Joe Conway") wrote in message news:<02a101c12c0e$37856d60$48d210ac@jecw2k1>... ... snip > BYTEA is very similar to TEXT, except that it is intended for binary data. I > recently posted a PHP function which escapes binary in order to allow > inserting it into a bytea column (on the pgsql-general list). At a minimum > there are 4 characters which must be escaped. They are ACSII 0, 10, 39, and > 92. They must reach PostgreSQL looking like \\000, \\012, \\047, and \\134 > respectively (actually 39 could be \' and 92 could be \\\\, but it is > simpler to be consistent). ... snip Is it actually necessary to escape \012 (linefeed) in a query? My brief testing using psql or python pygresql seemed to work ok with only \000, \', and \\ escaped. Gosh, maybe all my data is corrupted (!!) Ryan
В списке pgsql-hackers по дате отправления: