Changeset 6171


Ignore:
Timestamp:
Nov 12, 2010 7:46:16 AM (6 years ago)
Author:
robe
Message:

Update 9.0 FAQ to include npgsql fixed driver for bytea support

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/1.5/doc/faq.xml

    r6035 r6171  
    1111      <answer>
    1212        <para>In PostgreSQL 9.0+, the default encoding for bytea data has been changed to hex and older JDBC drivers still assume escape format. This has affected some applications
    13         such as Java applications using older JDBC drivers
     13        such as Java applications using older JDBC drivers or .NET applications that use the older npgsql driver
    1414                that expect the old behavior of ST_AsBinary.  There are two approaches to getting this to work again.</para>
    1515       
    1616        <para>You can upgrade your JDBC driver to the latest PostgreSQL 9.0 version which you can get from 
    1717            <ulink url="http://jdbc.postgresql.org/download.html">http://jdbc.postgresql.org/download.html</ulink></para>
     18        <para>If you are running a .NET app, you can use Npgsql 2.0.11 or higher which you can download from
     19                <ulink url="http://pgfoundry.org/frs/?group_id=1000140">http://pgfoundry.org/frs/?group_id=1000140</ulink> and
     20        as described on <ulink url="http://fxjr.blogspot.com/2010/11/npgsql-2011-released.html">Francisco Figueiredo's NpgSQL 2.0.11 released blog entry</ulink></para>
     21         
    1822        <para>If upgrading your PostgreSQL driver is not an option, then you can set the default back to the old behavior  with the following change:</para>
    1923        <programlisting>ALTER DATABASE mypostgisdb SET bytea_output='escape';</programlisting>
Note: See TracChangeset for help on using the changeset viewer.