Re: New release of psqODBC? - Mailing list pgsql-odbc

<pre style="margin: 0em;"><font face="Arial, Helvetica, sans-serif">Dave Page wrote:
</font></pre><blockquote style="border-left: 0.2em solid rgb(85, 85, 238); margin: 0em; padding-left: 0.85em;"><font
face="Arial,Helvetica, sans-serif"><tt> </tt><tt></tt></font><blockquote style="border-left: 0.2em solid rgb(85, 85,
238);margin: 0em; padding-left: 0.85em;"><pre style="margin: 0em;"><font face="Arial, Helvetica,
sans-serif">-----OriginalMessage-----
 
</font></pre> <font face="Arial, Helvetica, sans-serif"><tt>From: Hiroshi Saito [<a href="mailto:z-saito"
rel="nofollow">mailto:z-saito</a>( at ) guitar ( dot ) ocn ( dot ) ne ( dot ) jp] </tt><tt>Sent: 10 October 2006 17:19
</tt></font><pre style="margin: 0em;"><font face="Arial, Helvetica, sans-serif">To: Dave Page; Hiroshi Inoue
 
Cc: pgsql-odbc ( at ) postgresql ( dot ) org
Subject: Re: [ODBC] New release of psqODBC?

</font></pre><blockquote style="border-left: 0.2em solid rgb(85, 85, 238); margin: 0em; padding-left: 0.85em;"><font
face="Arial,Helvetica, sans-serif"><tt>From: Dave Page </tt><tt>I've never saw a reply to this question - can you
commentplease? </tt></font></blockquote><pre style="margin: 0em;"><font face="Arial, Helvetica, sans-serif">Hi Dave.
 

</font></pre> <font face="Arial, Helvetica, sans-serif"><tt>As for me, tests of 08.02.0102 of the present version is
not</tt><tt>completed yet. </tt></font> <pre style="margin: 0em;"><font face="Arial, Helvetica, sans-serif">1.) *nix
buildfor iODBC and unixODBC
 
2.) *nix build 64bit mode.
3.) MS build for VS2005.
4.) MS build 64bit mode.
5.) MSDTC...

</font></pre> <font face="Arial, Helvetica, sans-serif"><tt>Someone can help them. However, it was not necessarily
</tt><tt>decidedthat they </tt><tt>would be the specifications still opened wide. </tt></font><font face="Arial,
Helvetica,sans-serif"><tt>Inoue-san has included them and correcting the some bugs. </tt><tt>It seems that it becomes
theVersion 08.02.0103 edition. </tt></font></blockquote><pre style="margin: 0em;"><font face="Arial, Helvetica,
sans-serif">Well,we should really gather some of the bug fixes from 08.02.0100 into
 
an 08.02.0200 release ready for inclusion with pgInstaller. We can
always add further improvements in later versions.

</font></pre><blockquote style="border-left: 0.2em solid rgb(85, 85, 238); margin: 0em; padding-left: 0.85em;"><pre
style="margin:0em;"><font face="Arial, Helvetica, sans-serif">However, Inoue-san is very busy now....
 
</font></pre></blockquote></blockquote><pre style="margin: 0em;"><font face="Arial, Helvetica, sans-serif">>Sorry
forthe late answer.
 
>Unfortunately I can't solve the problems reported by Avery or Andrus yet.
>Anyway I would commit the changes in a day or 2.

>regards,
>Hiroshi Inoue
</font><font><font face="Arial, Helvetica, sans-serif">
Don't wait for me,</font></font> <font face="Arial, Helvetica, sans-serif">the empty date issue is about as resolved as
itwill get.  I've dug a little deeper into
 
ODBC and it seems that ODBC has no concept of "empty dates", so there really isn't a way to get the
driver to represent NULLs as empties when going PostgreSQL->ODBC->FoxPro.  However, converting
empties to NULL is a very practical approach and will be useful to several people. At least it works for
FoxPro->ODBC->PostgreSQL, and that solves all kinds of problems right there.  I would be so bold as
to even suggest that it become a default behavior in the driver, silently converting "empty dates" from
Microsoft data sources into NULL; this appears to be the default behavior for MS Access as well,
so I doubt it will cause issues.
</font></pre>