Thread: New release of psqODBC?

New release of psqODBC?

From
"Dave Page"
Date:
Hi Hiroshi,

I'd like to build a new release of psqlODBC to pick up the bug fixes
you've made from 08.02.0100, ideally before the next PostgreSQL beta
release. Do you have anything outstanding you'd like to finish/commit
before I do so?

Regards, Dave.

Re: New release of psqODBC?

From
"Andrus"
Date:
> I'd like to build a new release of psqlODBC to pick up the bug fixes
> you've made from 08.02.0100, ideally before the next PostgreSQL beta
> release. Do you have anything outstanding you'd like to finish/commit
> before I do so?

I noticed the following behaviours in Windows 98 computer using last
snapshot of Unicode
8.2.103 version driver:

1. When correct password is passed to driver, I got error

IM001 Driver does not  support this function

2. When incorrect password is entered, invalid page fault error occurs.

MYAPP caused an invalid page fault in
module PSQLODBC35W.DLL at 0167:10038813.
Registers:
EAX=10061600 CS=0167 EIP=10038813 EFLGS=00010297
EBX=00000020 SS=016f ESP=0063acc8 EBP=00000020
ECX=100616ec DS=016f ESI=017d4240 FS=18ff
EDX=0000002e ES=016f EDI=0000000f GS=0000
Bytes at CS:EIP:
8b 0b 89 4c 24 20 8b 86 58 01 00 00 85 c0 7f 07
Stack dump:
017d4240 00000001 fffffffe 017d4240 100616ec 10038d9b 10061618 10051403
017d4240 018e0400 00000000 10041076 017d4240 fffffffe 100616ec 10061618

3. 103 version of driver creates mylog file containing  single line even
when logging is turned off.

4. In Windows 98 it is not possible to uninstall 8.1 and 8.2 versions of
driver.
Unistallation finishes but psqlodbc entry remains in Add/Remove programs.

5. 8.1 and 8.2 driver installation creates same name: psqlodbc in add/remove
program list.

For ANSI 8.2.103 version of driver:

6. B9=0 option is not working. boolean columns are returned as
CHARACTER(254) type fields.


Andrus.



Re: New release of psqODBC?

From
Hiroshi Inoue
Date:
Andrus wrote:
>> I'd like to build a new release of psqlODBC to pick up the bug fixes
>> you've made from 08.02.0100, ideally before the next PostgreSQL beta
>> release. Do you have anything outstanding you'd like to finish/commit
>> before I do so?
>
> I noticed the following behaviours in Windows 98 computer using last
> snapshot of Unicode
> 8.2.103 version driver:
>
> 1. When correct password is passed to driver, I got error
>
> IM001 Driver does not  support this function

Could you send me the ODBC trace log ?
You can see how to trace the log at
 http://www.starquest.com/Supportdocs/techdocs/How_to_run_an_ODBC_trace.html .

> 2. When incorrect password is entered, invalid page fault error occurs.
>
> MYAPP caused an invalid page fault in
> module PSQLODBC35W.DLL at 0167:10038813.
> Registers:
> EAX=10061600 CS=0167 EIP=10038813 EFLGS=00010297
> EBX=00000020 SS=016f ESP=0063acc8 EBP=00000020
> ECX=100616ec DS=016f ESI=017d4240 FS=18ff
> EDX=0000002e ES=016f EDI=0000000f GS=0000
> Bytes at CS:EIP:
> 8b 0b 89 4c 24 20 8b 86 58 01 00 00 85 c0 7f 07
> Stack dump:
> 017d4240 00000001 fffffffe 017d4240 100616ec 10038d9b 10061618 10051403
> 017d4240 018e0400 00000000 10041076 017d4240 fffffffe 100616ec 10061618
>
> 3. 103 version of driver creates mylog file containing  single line even
> when logging is turned off.

Please retry the snapshot dll.

regards,
Hiroshi Inoue

Re: New release of psqODBC?

From
"Andrus"
Date:
Hiroshi,

>> 1. When correct password is passed to driver, I got error
>>
>> IM001 Driver does not  support this function
>
> Could you send me the ODBC trace log ?

ODBC log included.

>> 2. When incorrect password is entered, invalid page fault error occurs.
>> 3. 103 version of driver creates mylog file containing  single line even
>> when logging is turned off.
>
> Please retry the snapshot dll.

Those issues are fixed.
Thank you.

Andrus.


begin 666 odbclogfile.zip
M4$L#!!0````(`.!J/35ARG@S?08``"MQ```/`!$`;V1B8VQO9V9I;&4N;&]G
M550-``<$]!Q%T#<<15OT'$7MG5]/JT@8QJ\U\3M,O*HG.6:@0.EVW806JB0M
M] "UGAC3=)%ZFN,60]'=9+/??8<65%HM0PO.C)S>6,TXO,\S\_[F3\MP=#BY
MOWM<+,#S:SKU9%F"W&_HC="8",T#S7 T"]C?>LK]O>]J\R=P='AP<*$9E^ +
M2+W@/] 5>,C)PM'A$4[-5[H#4C6#OV?A#Q!XX6,P!ZY_ZP$(:JC V!YV.IIM
MGV1?&M2B7SC)Y<0F/,$,)"6QX\_GGAN^R 0;UXJK7Y90VYTWHH%2_4^W#G<Q
M(KD^OAE[!/ABE\3EMLOVPCA8\R&<^7/P?+VW(T*7B$H,1Z:EKA=9O3A87U8R
M5-\KPXDY/=T($L]72E24:#7';PU2@$V)`:N+4U%FK]X>9%2$A5Y=F(HR>S7,
M"C(OE(GTZL)4)%:KP>S)"V(A(TRC+T;&QM6CL0.]1$Z.2HPZ%XJU-KRLZH""
M+(/KU5^^UF_ L6KIEYIU]N_ 7X1W@8=B`L/Y+/+OOY:J.$I;L;4SSWN:M&S-
MBDK*PJD(3SE9/N5YJ34P+>=,%.I\:ZBKJ%PX6?C3L-5NGL'68*2>/?R<+!:S
MGY/@43R.(K/?MQ?%`[8'SS4X`634(L:-M"JR44LTP#9Y-Z.E45N#WZ.^LW)G
MW#'[@Y[F:'_D[*1KS;O91;E4%QV/=.=BK!M=$[.S5KLGK()';\L*/BM.O+X&
M:BC$DY)[7 *4<R_4YU-_?V0#(*4",I1^%,S!P<"Q-HHF8J&;E9Y $C(M@_)N
MHG'Y6:#J)(\R5'.\7)SJ!"[/JLL?^7:U)<9+':(,':#_-U$0=7%TJO9Z6;F%
M9QFHU;'71VN^46A;DD.Q;9R8WS:\_$)($O,N*XLC"]>(76GW[:IP)9=F5"?/
M>_#34V4G4^+DX)=,>1[MB\()3S-.=DJ<!";Y_,+F2.[MJ>(XTFBDZ!I1<HS>
M5( F.RBO"E/VL.9UID#^%,*BH(*?) 2@LD<6Q88!$=<P7*H0G)P(L1U#NSJ+
MGER:JP*2G4Q)$"*AC,#=1<"FB$0Q179*FX0?<@ZW<!$BDT,(:L^E%[J**M>[
M>K2=H]CO.Q(;6)<RDPK5335(&%%.`B>DK4%+&XKQP9 [)?"BN2'^V]!TM'&T
M_5V!Z<?.^JLR%=G;H&2@Y=% >US85@G-/-DWI1+'.!S'L#=+""YKXH^7.HJC
M],SSY11M;&L#Q5(<LPJ0V=V RBQXZ' (U&C>+:$DCW*85#Q+ZO&G6OUASQE;
MFAW]L#7'K@!%=I%>%7[LX\WK"<KW*DQ0]LFAUW.33+/*G)MT'^=N]-V[10&9
M)3;!2Y%WPLS[#?94B!_0J%@:B$X#Y7CX.M><Z%M18^W*T0Q;-XW,CB=/W<R5
M-MWL9D8["7B3-P?4!(IYS90_)2P?X^'*N3+0U'>@M'L8>W.9W]6E?3N;`=5$
M%HH$;:%[5L>(,\7S013C9;%I7&J6,V[K3C879<8G%/2+)D$'@J[0/85@PY@2
MV""E=>-LP7\".-"OF@@="-I".1[8<*8$/LAIX:K6T?M*KP*(8$(X$4J0=89R
M4#!C3@FL:*YI-X?;UEB?!Q4LZ"9""J+&4 X*5KPIGA,23$OO]DRE`CL2+,@F
M00FBOM -"5:L*8$17%JYCBYQGGWCTR>@!!/"B7""K#.4DX(9<TI@13VMW1CV
M-4OO5( 53 @GP@JRSE#."F;,*8$5C;1V1^]KMJ/T!Q6@!2/2B?""M#>4$X,A
M>THXRF1M%7:I6-7XF)0-X40.,B'K#-VT8,><$N87?%I[SS3.*\,+=L03F6.0
M=X?R6093!J4>@&"'?X68"71A.WWG[0!<?J>G'RPOOMD^7^/SBS7+,BW<,XN+
M""YQ1@L"/UBY@O?(!8S0-DK$KV7?>OM$XF7_\%#3&M_U$Q0.0)U W>P%JY(3
M^5;87M=$SKQ=D(="UDUPZ#IY0;VT<_2!?KYSPG,4O= 4\OFYK:Y)EI\<Y+.2
M-X>?2>[$?A;YS!!*#%_=@)QI>GQ$MQ =J7?=G[F!'YWQ=',=G3('5J>C@_YD
M/KGS@IOD]UO?6X"Y'X+%X\.#'X0@_#%;@&E\(U_&_8Z8[0AJ**:\X]0*-A0U
M9E$T2AHS@TCQ?:>-#VM,3,B!6B/WW?"_!HY?`P>+`P<'8]H8YGAY(V+7'!HJ
M@P,(S<;3Z/LG!TAG,G>]>X#C1;X'[,P6[NLGQV6T1+ZGN[S47<C2-9>P;N!Y
MG;*4O:[\XZ7EZ O_`U!+`0(6"Q0````(`.!J/35ARG@S?08``"MQ```/``D`
M``````$`( "V@0````!O9&)C;&]G9FEL92YL;V=55 4`!P3T'$502P4&````
/``$``0!&````NP8`````
`
end


Re: New release of psqODBC?

From
"Andrus"
Date:
Horoshi,

>> 2. When incorrect password is entered, invalid page fault error occurs.
>>
> Please retry the snapshot dll.

Previous message was incorrect: I'm able to reproduce the page fault  when
incorrect password is entered even in latest snapshot.
However, now the module where page fault occurs is in kerner32.dll
Log files included.

Andrus.


begin 666 pagefaultinkernel.zip
M4$L#!!0````(`)NF/35$#+B0S04``'X?```4`'T`;7EL;V=?-#(Y,S$U.#(R
M.2YL;V=31&@`O `````(`%4;=#9C9&!I$6%@8#!@@ `?(&9D!3-918'$;JY;
M@L]/WZWM6FYD_YH9MQPC$P,#$T,!`PM(5D""X3^C/ -(#*16`4@H@-@"(A!Q
M1HBX$%BM"D0,CYT@\U8R"*&8IPAD`P!55 T`!W9='4507AU%4%X=1>5947/:
M.!!^OOP*3?O@Y(8PMH%@X-09$DB;F31)(;D\9!A&V#+UG+&I)*=);^Z_WZZ-
M@PPDH3G:TBL/C&2M5M^W*^W*ZYM]JV$=.$YE, [C$0MEF=\IP8;R7BHV"OEP
M*K@?W'%)*#$\;]@R=FX>IO [3B(VX;1]^O:JW]=&;F[Z'T[;81B[[UCDA7PP
MF(_]#C\21.3B;?OB9)@*=:-;`@]W="'"[P*U(-0DTX\<9"FQ'&[RB@FS%E?M
M<P62;:7$8$"84M0VS9*])C9MN:,XBKBKFH1'BHL@&I?+Y9T%%JO$BP!+Q(4!
M[->]JETU-0W=LR$#B[K9Q"".FD3RT%]K+LE^,)][0)($A,[$]]^L`B!O@L'B
MB&X2L,A;KDXB/[[>K9A[2Q:9#1:,X>.3R_LII_7ZSJ,3IM0P*^6:991(R"-$
M><O"A*=P1^_9';7L!2#@P)DQT8G72UB*X\2/16Z@)K%,FUA+8.8SSJ>9H7,:
MQ,^>H%5@ZNT%$VR"G8UBJA#_I9@J&J;:)D%98"C3-%^(R])L534;!PO(.B*X
MY6*F9QE887B-`[8@[^?]R33DB(A:V2[O*W$24:/3._FSVZ-_7\12C04'/.0J
M"MS8X_^TKDXZE'/%9.RKUL5UA]X]_%J=]F7[L-WO@L M:_6[/=3B5,LULVPY
M3MFV#UH7Y[U+6JM6[-9A@YJ%8!@G(C_+0ZE2@T'(_#%8(.R)8)0H/H=@S X>
M/EF%1I_NQM/[=JY"-DFG?T8-HR2Y`+-CRQLQR;&1R.S!E$GYV:-&"AZZL5#X
M.([">\&9EXJ(6,5N'&(;[3247"FPDDP5!I)!%/V,Z6;"5"(XW;?V'F,$AM/I
MY#;\+Q0>='QG*N!VG4JVZ$_((]^O1;_<LI=P2>?]8#[9B=/9% [?5] JSMLF
MCAA =(882[XGL72];T7NL*%3,W]F7F.N`&*07J<0*XD!YV<1*+A%_3\3T!%X
M"-+[)(YT/[7K%*XLK;9#\<K1:N.BAR:U:]76H44=JP%=FUJMPPH.5+%5P[\#
M[-:QY6"K`:TC$UI'%O[9%%]K7IYIM@;K<ZED:X"NDRNV!NQ7)(+MV0G/!/:M
M`?I$D/[&&,VG,+H0CS%\9H'7XSY+0B5U<$=YI'WL[47*< )1C6)P'X5<#],B
M& <1"X?/*UDI"HC06&"X+&$M;\D2P3STX/@2\9ABF,4>#EJ)8"+#TDTAJL%$
MS&>Q>,AHA:R9U2G +BHFZB//UY>Q^Q=71>2[YMYNE(3A'NGV>F?GA3PU+WBL
M5$1DXKJ<>]PKV#/XPF.?2,6$2J: ,Q6EI.'H0F#&5"%+X#]2@<O2948A:,[T
M2ND#K'M=]1CP,.+%"[,T"4SC9!]>,K,:V3 #.APEOL\%(J,+[\"G3((_12QP
MMU9JBZJLROJJ$!09QXH8O4*"%?P3T*\1N#LH6O,:C9I=KQ3>YX.(M*\NWPU[
MW0_#]YTE$!ODTW!>PJ=K/+?5083LD_XQY(O3]62/;*=8U'A"]GV^V1>WB\^"
MD'MIO02/"7F5'Y!7ZRD^1GUE=SWATTJEOIYD#]4.,W#%6)2Z!NY\3/$)\)!9
M(9$NEPV/SL_.\$2>]YK$3R*7KE@.P@67+EY,">B-D@FU+3-M3^28&JDSFN3K
M;6<\A6-%G2?'T45RQ!?QA #(V>"W!#<KAG8"-NYQ=[EZ-1^;E\84ED%M(KA+
M]=*A5L.:`4_9-,E';^3F_B%_F&_THCKJ1*J0?3+/KAITX> IGHT#=4T$>AC4
M-V**M 3_Y&JYQ"JP^N,FAFZ5X&>$U&,9RM<O1OE:6^>WM!8NO_0_A7T\`T@_
MC0-&"4O.M3JDRB^IX:F1926=X[)3@1+Z=+$&_'WW1*VQ_J;84A_,;+WLA(WL
MS4?]5OBPH3GN.."A=ST8D.RS#]VU2S-K[Y$>.HF<>-0A^)Y-=\V2N??88JFB
MN9]3!S\MNF)';4;C1KA:!ZYY8#J_`./&+^3=AN9=YY?PKF7^;.[]%U!+`P04
M````" "DICTU<UCO)AP!``#T`0``#0!]`'!A9V5F875L="YT>'131&@`O ``
M```(`%4;=#9C9&!I$6%@8#!@@ `?(&9D!3-918'$;JY;@L]/WZWM6FYD_YH9
MMQPC$P,#$T,!`PM(5D""X3^C/ -(#*16`4@H@-@"(A!Q1HBX$%BM"D0,CYT@
M\U8R"*&8IPAD`P!55 T`!X1='4537AU%4UX=17607VO",!3%WPO]#N<3R$W3
MOT(?K(TB*T,,`U]CVHI,G:SM8-]^2:K='F8@X>;PNR?G9E&MWZ2$5D/7U%!7
MG*Y?ZGRJ<5/'!JT:SKV1?._R40_G!B]B]RHJ'LS*JH+J02Q.YH>V311/LIGO
M[9KCJ>N;SV[N>V*QSXGBR&R-I<PM"['9Y@\>8E6MC4[$**# =!1[2VE&+(5T
M'2V$W%H;KK1*(8K'16O#+]T+F=D,Y<1OK*5SQ4KF(?'$H.5H;76#W-'2HG'L
MT#$)^5[QW3>='6XIYR:NF23-$#)0BO2 B(-"6X3<*1DB<DIM3\[MU?=DK_0[
MZN%R,^W3$W1?N"?1F")-8_\R?PM6!VPL8AU@_($VA/O)R&9[XL/H'\,?4$L!
M`A8+% ````@`FZ8]-40,N)#-!0``?A\``!0`$0```````0`@`+:!`````&UY
M;&]G7S0R.3,Q-3@R,CDN;&]G4T0$`+P```!55 4`!W9='4502P$"%@L4````
M" "DICTU<UCO)AP!``#T`0``#0`1```````!`" `MH%\!@``<&%G969A=6QT
K+G1X=%-$! "\````550%``>$71U%4$L%!@`````"``(`GP```$ (````````
`
end


Re: New release of psqODBC?

From
"Dave Page"
Date:

> -----Original Message-----
> From: Dave Page
> Sent: 28 September 2006 08:14
> To: Hiroshi Inoue
> Cc: pgsql-odbc@postgresql.org
> Subject: New release of psqODBC?
>
> Hi Hiroshi,
>
> I'd like to build a new release of psqlODBC to pick up the
> bug fixes you've made from 08.02.0100, ideally before the
> next PostgreSQL beta release. Do you have anything
> outstanding you'd like to finish/commit before I do so?

Hiroshi,

I've never saw a reply to this question - can you comment please?

Thanks, Dave

Re: New release of psqODBC?

From
"Hiroshi Saito"
Date:
> From: Dave Page
> I've never saw a reply to this question - can you comment please?

Hi Dave.

As for me, tests of 08.02.0102 of the present version is not completed yet.

1.) *nix build for iODBC and unixODBC
2.) *nix build 64bit mode.
3.) MS build for VS2005.
4.) MS build 64bit mode.
5.) MSDTC...

Someone can help them. However, it was not necessarily decided that they
would be the specifications still opened wide.

Inoue-san has included them and correcting the some bugs.
It seems that it becomes the Version 08.02.0103 edition.
However, Inoue-san is very busy now....

Regards,
Hiroshi Saito




Re: New release of psqODBC?

From
"Dave Page"
Date:

> -----Original Message-----
> From: Hiroshi Saito [mailto:z-saito@guitar.ocn.ne.jp]
> Sent: 10 October 2006 17:19
> To: Dave Page; Hiroshi Inoue
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] New release of psqODBC?
>
> > From: Dave Page
> > I've never saw a reply to this question - can you comment please?
>
> Hi Dave.
>
> As for me, tests of 08.02.0102 of the present version is not
> completed yet.
>
> 1.) *nix build for iODBC and unixODBC
> 2.) *nix build 64bit mode.
> 3.) MS build for VS2005.
> 4.) MS build 64bit mode.
> 5.) MSDTC...
>
> Someone can help them. However, it was not necessarily
> decided that they
> would be the specifications still opened wide.
>
> Inoue-san has included them and correcting the some bugs.
> It seems that it becomes the Version 08.02.0103 edition.

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.

> However, Inoue-san is very busy now....

:-(

Cheers, Dave

Re: New release of psqODBC?

From
"Joshua D. Drake"
Date:
>>
>> Inoue-san has included them and correcting the some bugs.
>> It seems that it becomes the Version 08.02.0103 edition.
>
> 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.

The current 08.02. tarball (not cvs) also does not compile on 64bit linux.

Joshua D. Drake


>
>> However, Inoue-san is very busy now....
>
> :-(
>
> Cheers, Dave
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>                http://archives.postgresql.org
>


--

   === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
   Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/



Re: New release of psqODBC?

From
Hiroshi Inoue
Date:
Dave Page wrote:
>
>
>> -----Original Message-----
>> From: Hiroshi Saito [mailto:z-saito@guitar.ocn.ne.jp]
>> Sent: 10 October 2006 17:19
>> To: Dave Page; Hiroshi Inoue
>> Cc: pgsql-odbc@postgresql.org
>> Subject: Re: [ODBC] New release of psqODBC?
>>
>>> From: Dave Page
>>> I've never saw a reply to this question - can you comment please?
>> Hi Dave.
>>
>> As for me, tests of 08.02.0102 of the present version is not
>> completed yet.
>>
>> 1.) *nix build for iODBC and unixODBC
>> 2.) *nix build 64bit mode.
>> 3.) MS build for VS2005.
>> 4.) MS build 64bit mode.
>> 5.) MSDTC...
>>
>> Someone can help them. However, it was not necessarily
>> decided that they
>> would be the specifications still opened wide.
>>
>> Inoue-san has included them and correcting the some bugs.
>> It seems that it becomes the Version 08.02.0103 edition.
>
> 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.
>
>> However, Inoue-san is very busy now....

Sorry for the 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


Re: New release of psqODBC?

From
"Dave Page"
Date:

> -----Original Message-----
> From: Hiroshi Inoue [mailto:inoue@tpf.co.jp]
> Sent: 11 October 2006 03:27
> To: Dave Page
> Cc: Hiroshi Saito; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] New release of psqODBC?
>
> Sorry for the 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.

OK, thanks - please let me know when you are happy for me to bundle a
release.

Regards, Dave.

Re: New release of psqODBC?

From
Avery Payne
Date:
<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>