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?

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Re: New release of psqODBC?

> 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.



---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Re: New release of psqODBC?

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

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Re: New release of psqODBC?

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.




---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Re: New release of psqODBC?

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.




---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Re: New release of psqODBC?

=20

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

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Re: 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.
However, Inoue-san is very busy now....

Regards,
Hiroshi Saito




---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Re: New release of psqODBC?

=20

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

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

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Re: New release of psqODBC?

>>
>> 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/



---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Re: New release of psqODBC?

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


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Re: New release of psqODBC?

=20

> -----Original Message-----
> From: Hiroshi Inoue [mailto:inoue@tpf.co.jp]=20
> Sent: 11 October 2006 03:27
> To: Dave Page
> Cc: Hiroshi Saito; pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] New release of psqODBC?
>=20
> Sorry for the late answer.
> Unfortunately I can't solve the problems reported by Avery or=20
> 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.

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Re: New release of psqODBC?

Dave Page wrote:

-----Original Message-----

To: Dave Page; Hiroshi Inoue

Cc: pgsql-odbc ( at ) postgresql ( dot ) org

Subject: Re: [ODBC] New release of psqODBC?

Hi Dave.

1.) *nix build for iODBC and unixODBC

2.) *nix build 64bit mode.

3.) MS build for VS2005.

4.) MS build 64bit mode.

5.) MSDTC...

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



Don't wait for me, 
 face="Arial, Helvetica, sans-serif">the empty date issue is about as resolved as it will 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.