Search Postgresql Archives

Re: PQexec(), what should I do for the "NULL in command" problem?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Nov 12, 2007 11:13 PM, Martijn van Oosterhout <kleptog@xxxxxxxxx> wrote:
> On Thu, Nov 08, 2007 at 06:39:23PM -0800, jason wrote:
> > As you know the interface of PQexec():
> > PGresult *PQexec(PGconn *conn, const char *command);
> >
> > "command" contains  some SQL statements.
> >
> > But there exist "\0" in some data filed, and I found PQexec() failed
> > on such situation.

Thanks for reply :-)
But would you please give me more details or some references?

> Two ways:
> - out of line parameters
How to? Is there any function for this? I mean the C interface.

> - escape the nulls, like \0
Do you mean this function?
#unsigned char *PQescapeBytea(const unsigned char *from,
#				 size_t from_length,
#				 size_t *to_length);

But after the "escape", the data is changed, and it cannot
automatically change back when insert them into database.
I have to "unescape" it when query. Is this necessary?

Best Regards,
Jason

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux