On 2012-09-11, Raymond O'Donnell wrote:
>
> BTW, it's a REALLY bad idea to build literal SQL queries from input
> values, as you're doing - you should use parameters and
> pg_query_params() instead.
Although (still) marked "experimental"
pg_insert and pg_update work really well
the more recent p
On 11/09/2012 20:42, Alexander Reichstadt wrote:
> Thanks for the push, I found the information I needed. It works now.
Glad you got sorted. For people looking at the archives, what was the
problem, and how did you fix it?
Ray.
--
Raymond O'Donnell :: Galway :: Ireland
r...@iol.ie
--
Sent v
On 11/09/2012 14:24, Alexander Reichstadt wrote:
>
>
> What am I doing wrong?
>
What version of PG are you using? The default output format of bytea
changed from "escape" to "hex" a version or two ago - try changing it to
"escape" and see if that makes a difference:
ALTER DATABASE x SET
On 09/11/12 6:24 AM, Alexander Reichstadt wrote:
What am I doing wrong?
I'm not a php programmer (hate the sloppy stuff) but nowhere do I see
you specifying a mime image type for your image data being returned to
the browser.
this is a php problem, not a postgres problem.
--
john r pierce
Sorry if this has been asked a thousand time. I read through the web and think
to have done everything I should.
I have a db with a bytea field. In it I stored data from a png file. When I
stored it I used pg_escape_bytea() and it seems it ended up
ok in the database.
I made a test setup, che
Sorry if this has been asked a thousand time. I read through the web and think
to have done everything I should.
I have a db with a bytea field. In it I stored data from a png file. When I
stored it I used pg_escape_bytea() and it seems it ended up
ok in the database.
I made a test setup, che
