Latest Npgsql version 2.0.11 already has a fix to handle new bytea representation. Can you try with this version and see if it works ok? I hope it helps. On Tue, Dec 14, 2010 at 14:22, tuanhoanganh <hatuan05@xxxxxxxxx> wrote: > Thanks for your answer. But I don't want to change db config or ALTER > DATABASE data SET bytea_output='escape'; > I can change my app. So is there document introduce how to work with > postgresql 9 bytea ( I don't want to user lo_create, lo_import. lo_export) > > Tuan Hoang Anh > > On Tue, Dec 14, 2010 at 8:55 PM, Ivan Voras <ivoras@xxxxxxxxxxx> wrote: >> >> On 14/12/2010 14:51, tuanhoanganh wrote: >>> >>> Thanks for your help. >>> Is there any .Net or VB tutorial new 9.0 bytea? >> >> You do not need to change your code if you add >> >> bytea_output = 'escape' Â Â Â Â Â Â Â Â # hex, escape >> >> into postgresql.conf. >> >> >> >> -- >> Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-general > > -- Regards, Francisco Figueiredo Jr. Npgsql Lead Developer http://www.npgsql.org http://fxjr.blogspot.com http://twitter.com/franciscojunior -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
