Magnus Hagander <[EMAIL PROTECTED]> writes:
> On Sat, 2007-11-17 at 21:13 +0100, Thomas H. wrote:
>>> I'll bet a nickel that you built one version with float timestamps and
>>> the other with integer ...
>>
>> both versions are the official win32 builds from postgresl.org...
> That means Tom is r
On Sat, 2007-11-17 at 21:13 +0100, Thomas H. wrote:
> tom lane wrote:
> >> i'm not sure it its really a bug - the manual specifies that COPY ...
> >> BINARY between different PGSQL versions might be problematic.
> >
> >> nevertheless: i've imported several tables from 8.2.5 to 8.3b2 without
> >
On Fri, 2007-11-16 at 06:34 +0100, Christian Ullrich wrote:
> * Magnus Hagander wrote:
>
> > Christian Ullrich wrote:
>
> >> psql tells me about an "invalid frontend message type 112". Most of the
> >> time, that error comes as the first line of output from psql (above the
> >> "Welcome to" line
On Fri, 16 Nov 2007, Lance J. Andersen wrote:
The table in this case that needs to be looked at is B-5, not B-4 which i
believe you are referring to. The expectation of setObject(int/String,
Object, int) is that you are sending the value to the backend as the SQL
Type specified for the 3rd
