psqlODBC 09.00.0310 Released

We are pleased to announce the release of psqlODBC 09.00.0310.

Changes and updates in the new release include:

1.) Let SC_forget_unnamed() clear the result in case the statement is
not executed yet. It would fix the bug reported by Silvio Brandani.
2.) Fix the bug that strings are copied to a null pointer.
3.) Don't clear the parsed plan in SC_recycle_statement().
4.) Now SQLDescribeCol() can detect the changes of column type or size.
5.) Handle *with or without oids* correctly.
6.) Take the environment variable into account.
7.) Use SOCK_get_next_n_bytes() instead of SOCK_get_next_byte().
8.) Add some driver specific options for SQLSetConnectAttr().
9.) Fix compilation errors in case ODBC 2.5.
10.) Fix compilation error on different ODBCVER.
11.) Correct the behavior of SQLSetConnectAttr() for the driver specific
options.

psqlODBC may be downloaded from
http://www.postgresql.org/ftp/odbc/versions/ in source, Windows
Installer, merge module, and basic zip file formats.

Please post any bug reports to the pgsql-odbc@postgresql.org mailing list.

I'd like to take this opportunity to thank all those involved with the
development, testing and bug fixing of the updated driver.

--
psqlODBC team.

--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: psqlODBC 09.00.0310 and oids

--nextPart2494906.zJkXyyK9Cr
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Friday 08 July 2011 21:08:21 Hiroshi Saito wrote:
> Changes and updates in the new release include:
> 5.) Handle *with or without oids* correctly.

Thank you very much.
However, the behaviour is still no exactly what I expected:

I have a legacy excel 97 database, poorly designed, with about 100 tables, =
1000 queries, complex forms... You get the picture.
I used a recent mdbtools snapshot from git to convert the database to postg=
res (index, default values, constaints, this rocks!).
However, I had a lot of tables without a primary keys.
What I did is adding oids for these tables, and created a primary key (on o=
id).

Now, I still have some legacy code from access I'd like to use.
I changed the access tables to psql linked tables, and I'm opening the conn=
ection with that:
ODBC;CA=3Dr;A6=3D;A7=3D100;A8=3D4096;B0=3D255;B1=3D8190;B9=3 D0;BI=3D0;C2=3D=
dd_;CX=3D1b102bb;A1=3D8.4;DSN=3Dindia;SERVER=3D10.10.10.146; DATABASE=3Dindi=
a;PORT=3D5432;UID=3Djvourger;PASSWORD=3Dxxxxxxxx
(This is CX with BIT_SHOWOIDCOLUMN)
But when open these tables with a primary key on oid, I don't see the oid c=
olumn and I can't append data.

I also tried CX=3D1d102bb (BIT_FAKEOIDINDEX). Same results.

Does anyone has any idea about what is going on?
Is that an excel problem? Or is there some change I could make in psqlodc t=
o have these linked tables work with legacy access modules?

=2D-=20
=2D - Nirgal Vourgère â˜=AE GP France â˜=AE tel:+33.180969724
=2D xmpp:nirgal@nirgal.com â˜=AE gpg 0x4760b41db292ab13 â˜=AE sky=
pe:nirgal_v
nirgal.com:qotd â˜=AE Be the change you want to see in the world --=
Gandhi

--nextPart2494906.zJkXyyK9Cr
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk4cE0YACgkQR2C0HbKSqxNkYQCeJU/9iqqOQPo9x6mF3TJR nNAE
Sl0AoLfI7hLC/MwRJlj6VNgZFZ3ACi/U
=vq6O
-----END PGP SIGNATURE-----

--nextPart2494906.zJkXyyK9Cr--

Re: psqlODBC 09.00.0310 and oids

Hi Nirgal-san.

Sorry very late reaction.

Umm, I can't explore your problem....
Office 97 is very old which does not reach it for me.
although I use 2003, I don't look at a problem.
For example,
http://winpg.jp/~saito/psqlODBC/check/FakeIndex.png

Regards,
Hiroshi Saito

(2011/07/12 18:26), Nirgal Vourgère wrote:
> On Friday 08 July 2011 21:08:21 Hiroshi Saito wrote:
>> Changes and updates in the new release include:
>> 5.) Handle *with or without oids* correctly.
>
> Thank you very much.
> However, the behaviour is still no exactly what I expected:
>
> I have a legacy excel 97 database, poorly designed, with about 100 tabl=
es, 1000 queries, complex forms... You get the picture.
> I used a recent mdbtools snapshot from git to convert the database to p=
ostgres (index, default values, constaints, this rocks!).
> However, I had a lot of tables without a primary keys.
> What I did is adding oids for these tables, and created a primary key (=
on oid).
>
> Now, I still have some legacy code from access I'd like to use.
> I changed the access tables to psql linked tables, and I'm opening the =
connection with that:
> ODBC;CA=3Dr;A6=3D;A7=3D100;A8=3D4096;B0=3D255;B1=3D8190;B9=3 D0;BI=3D0;C=
2=3Ddd_;CX=3D1b102bb;A1=3D8.4;DSN=3Dindia;SERVER=3D10.10.10. 146;DATABASE=3D=
india;PORT=3D5432;UID=3Djvourger;PASSWORD=3Dxxxxxxxx
> (This is CX with BIT_SHOWOIDCOLUMN)
> But when open these tables with a primary key on oid, I don't see the o=
id column and I can't append data.
>
> I also tried CX=3D1d102bb (BIT_FAKEOIDINDEX). Same results.
>
> Does anyone has any idea about what is going on?
> Is that an excel problem? Or is there some change I could make in psqlo=
dc to have these linked tables work with legacy access modules?
>


--=20
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc